2011/7/2 Benjamin Kaduk <ka...@mit.edu>: > There is a functional difference between '-nostdinc -I/usr/include -I.' even > when the standard include search path is just /usr/include -- the standard > include paths are always searched last (unless -nostdinc is given), even if > they are explicitly listed on the command line. If there are conflicting > definitions in /usr/local/foo.h and ./foo.h, this gimmick can be necessary > to pull in the correct version. (I've needed to do this when packaging > software for the freebsd ports collection, though with /usr/local/include > replacing '.'.)
In this case I'd rather be safe than sorry and use -iwithprefix or -isystem `gcc --print-file-name=` on GCC only. What is the recommended way to check the compiler flavour and version from FreeBSD Makefiles? -- Robert Millan _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
