This is the mail archive of the mailing list for the GCC 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]


In message <>, "John David Anglin
" writes:
 >> > Really the way to go is to get HP to fix the hpux header files so that ne
 >> > fixincludes nor fixproto are necessary.  Then it becomes a hell of a lot 
 >> > to use tools built under one rev of the OS with newer revs of the OS.
 >> I guess I can see that, are there any platforms where this can be done
 >> today?  I am curious how they handle some of the generic fixincludes
 >> changes like mapping va_list and __va_list to __gnuc_va_list.
 >A better way is to dynamically fix header files.  This was suggested
 >in the discussion regarding the change to the header search implementation.
I didn't follow that discussion, but it's a pretty slick idea.  It would
solve the problem of how to deal with installing vendor patches which tweak
header files after GCC was installed.

Do you know if anyone is working on this?

 >One way might be similar to that used for web pages in browsers.  If
 >a header "changes", a cache of fixes could be updated.  As a result,
 >gcc wouldn't get out of date.  The private include directory of gcc
 >would disappear.
It wouldn't totally disappear as GCC still has its own varargs, stddef
and a few other header files.  But what would disappear would be the
slightly modified copies of the vendor's include files.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]