On Wed, 29 Jan 2003, James Turner wrote:
> Apparently, this can cause very obscure breakage (don't ask me to
> provide an example). As a result, GCC 3.2 prints out a *huge* warning
> for every single source file it processes, which is very, very
> annoying. Hence, the correct solution is only to add /usr/local/include
> (or lib) on systems where it is not already in the search path. Which,
> it sounds like, includes cywgin.
If you configure with
./configure --prefix=/usr/local
it will automatically work. At least, it does for me :-)
I hate it when compiler makers start trying to outsmart the user.
Anything other than /usr/include should not be in the default include
path, and anything the user provides should be trusted (and if libtool
screws up, libtool should be fixed, not gcc).
Oh well. Microsoft doesn't have a patent on innovation, and innovation
ain't always for the better ;-)
Cheers,
-- Bert
--
Bert Driehuis -- [EMAIL PROTECTED] -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
