Re: acl: FTBFS on GNU/Hurd
On Fri, Oct 10, 2003 at 09:16:19PM +0000, Robert Millan wrote:
> +#define __USE_LARGEFILE64
If the two underscores are not a hint enough for you, here it is in clear:
You are not allowed to mess with __* symbols in glibc.
There is an official interface, and it is _LARGEFILE_SOURCE and
_LARGEFILE64_SOURCE. Probably acl already can define that if it is needed,
check the configure script and other places for that. There is nothing in
the GNU/Hurd's large file support that is different from GNU/Linux's,
because it's the same glibc (at least as far as the interfaces are
concerned).
> +#define __USE_XOPEN_EXTENDED
See above. There are two relevant symbols:
_XOPEN_SOURCE Includes POSIX and XPG things. Set to 500 if
Single Unix conformance is wanted, to 600 for the
upcoming sixth revision.
_XOPEN_SOURCE_EXTENDED XPG things and X/Open Unix extensions.
You can not just define away things blindly just to make it compile. First
of all, you must use official interfaces. Second of all, you must
investigate why it doesn't work without this hack on the GNU/Hurd already,
because there shouldn't be any difference to GNU/Linux. Inspect where the
problem lies, and fix the root of it.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org marcus@gnu.org
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/
Reply to: