../compat/rbtree.h:50:10: fatal error: sys/endian.h: No such file or directory
50 | #include <sys/endian.h>
| ^~~~~~~~~~~~~~
../compat/rbtree.h:50:10: fatal error: sys/endian.h: No such file or directory
50 | #include <sys/endian.h>
Probably <endian.h> can be used instead?
../compat/rbtree.h:50:10: fatal error: sys/endian.h: No such file or directory
50 | #include <sys/endian.h>
Probably <endian.h> can be used instead?
Would you have a patch I could test on Debian and later submit to upstream?
(non-subscriber; please keep me in CC)
On Fri, Jul 1, 2022 at 6:31 PM Martin-Éric Racine <[email protected]> wrote:
../compat/rbtree.h:50:10: fatal error: sys/endian.h: No such file or directory
50 | #include <sys/endian.h>
Probably <endian.h> can be used instead?
Would you have a patch I could test on Debian and later submit to upstream?
This seems to be the relevant ./configure fragment:
*****
if [ -z "$BE64ENC" ]; then
printf "Testing for be64enc ... "
cat <<EOF >_be64enc.c
#include <sys/endian.h>
#include <stdlib.h>
int main(void) {
be64enc(NULL, 0);
return 0;
}
EOF
if $XCC _be64enc.c -o _be64enc 2>&3; then
BE64ENC=yes
else
BE64ENC=no
fi
echo "$BE64ENC"
rm -f _be64enc.c _be64enc
fi
if [ "$BE64ENC" = no ]; then
echo "#include \"compat/endian.h\"" >>$CONFIG_H
fi
*****
From what I could google, __GNU__ or __MACH__ might be possiblechoices, but I'm not sure which one applies here.
Actually, where it barfs is here:
#if !defined(__linux__) && !defined(__QNX__) && !defined(__sun)
#include <sys/endian.h>
#else
#include "endian.h"
#endif
What is the equivalent define for Hurd?
Martin-Éric Racine, le jeu. 28 juil. 2022 21:30:42 +0300, a ecrit:
Actually, where it barfs is here:
#if !defined(__linux__) && !defined(__QNX__) && !defined(__sun)
#include <sys/endian.h>
#else
#include "endian.h"
#endif
What is the equivalent define for Hurd?
It's just the same on the Hurd as on Linux, since that's just coming
from glibc.
On Thu, Jul 28, 2022 at 10:38 PM Samuel Thibault <[email protected]> wrote:
Martin-Éric Racine, le jeu. 28 juil. 2022 21:30:42 +0300, a ecrit:
Actually, where it barfs is here:
#if !defined(__linux__) && !defined(__QNX__) && !defined(__sun)
#include <sys/endian.h>
#else
#include "endian.h"
#endif
What is the equivalent define for Hurd?
It's just the same on the Hurd as on Linux, since that's just coming
from glibc.
Yet it FTBFS on Hurd at that precise point. That suggets we need to
patch that spot. Not knowing Hurd, I have no idea what the correct
fragment would be.
On Fri, Jul 29, 2022 at 2:09 AM Martin-Éric Racine <[email protected]> wrote:
On Thu, Jul 28, 2022 at 10:38 PM Samuel Thibault <[email protected]> wrote:
Martin-Éric Racine, le jeu. 28 juil. 2022 21:30:42 +0300, a ecrit:
Actually, where it barfs is here:
#if !defined(__linux__) && !defined(__QNX__) && !defined(__sun) #include <sys/endian.h>
#else
#include "endian.h"
#endif
What is the equivalent define for Hurd?
It's just the same on the Hurd as on Linux, since that's just coming
from glibc.
Yet it FTBFS on Hurd at that precise point. That suggets we need to
patch that spot. Not knowing Hurd, I have no idea what the correct
fragment would be.
If you want the Mach kernel, use __MACH__. If you want GNU Hurd, use
__GNU__ or __gnu_hurd__.
The Pre-defined Operating System Macros list at Sourceforge is usually reliable. Also see
https://sourceforge.net/p/predef/wiki/OperatingSystems/ .
"Hurd is not a supported OS. At a minimum it would need an equivalent
of if-bsd.c being ported."
Does that ring any bell?
Martin-Éric Racine, le ven. 29 juil. 2022 10:35:38 +0300, a ecrit:
"Hurd is not a supported OS. At a minimum it would need an equivalent
of if-bsd.c being ported."
Does that ring any bell?
The Hurd has a very BSD-ish interface, so starting from if-bsd.c is
probably a good idea.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 166:41:13 |
| Calls: | 12,096 |
| Calls today: | 4 |
| Files: | 15,003 |
| Messages: | 6,517,808 |