In reading through the gcc 3.3 release notes, I saw something that might explain some of our issues with building packages on Panther (and possibly Jaguar with the xcode update). They had this note:

---(snip!)---
The method of constructing the list of directories to be searched for header files has been revised. If a directory named by a -I option is a standard system include directory, the option is ignored to ensure that the default search order for system directories and the special treatment of system header files are not defeated.
---(snip!)---


Because of our "don't mess with the base system" approach, we often have to use -I to override/trick things into working the way we want, which sometimes includes forcibly using the system versions of things. I can imagine this causing issues if we're no longer able to override system directories to put "clean" system headers in front of our own.

Not sure what I want to accomplish with this note, other than a "head's up" I suppose. It may come back to bite us.

--
We put a lot of thought into our defaults.  We like them.  If we
didn't, we would have made something else be the default.  So keep
your cotton-pickin' hands off our defaults.  Don't touch.  Consider
them mandatory.  "Mandatory defaults" has a nice ring to it.



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to