This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tuesday 16 December 2008 17:14:33 Roland McGrath wrote: > > Roland McGrath wrote: > > > and why? > > > > Because it's unacceptable to require all those unnecessary changes just > > because hurd does something for no reason differently. > > That is not an answer to the question I asked. I'm talking about the > comprehensibility of the existing code, not about the Hurd code. > > Where does the existing code include kernel-features.h indirectly and why > does it rely on that implicitly? i dont think there is any documentation on this. basically, if you want to compile code for any port/arch, it has to have headers that implicitly include other headers exactly like a port drepper builds for (so like x86/x86_64). he's made it clear multiple times on this list when other arches randomly fail because x86/x86_64 pull in a bunch of standard headers at random places while other ports do not. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |