#2229: GCC fixincludes ----------------------------------------+----------------------------------- Reporter: [EMAIL PROTECTED] | Owner: [email protected] Type: defect | Status: new Priority: high | Milestone: 6.4 Component: Book | Version: SVN Severity: normal | Resolution: Keywords: | ----------------------------------------+----------------------------------- Comment (by [EMAIL PROTECTED]):
This is not an issue, and is intended by the GCC devs. We _could_ make it go away, but there will possibly be two (or more) directories added in the future. The extra directory needs to be explained in detail, however. Here is my understanding of it and attempt at keeping it simple, hopefully not over simplified (double check the names as I just started a fresh build and am going completely off of memory ATM): Whether or not gcc needs to run the fix includes script, limits.h is unconditionally installed into the gcc private directory include-fixed. If the system's installed limits.h is good for general consumption (when using latest available), there is no need to 'fix' it. limits.h, as installed into the gcc private directory, contains #include "syslimits.h". syslimits.h is also in the private include-fixed directory, which simply includes the system installed limits.h file from the standard include path (#include_next <limits.h>). There is a related, but different issue WRT the search path in chapter 5 gcc that will be fixed this weekend. -- Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2229#comment:1> LFS Trac <http://wiki.linuxfromscratch.org/lfs/> Linux From Scratch: Your Distro, Your Rules. -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
