On Wed, 08 Mar 2017 16:39:50 +0100 Dag-Erling Smørgrav <[email protected]> wrote: > 4) Remove the hardcoded library path in lang/gcc* > > This makes it possible to work on software that includes both libraries > and programs while an earlier copy of the same software is already > installed. With the current state of gcc, the programs you are working > on will be linked against the version of the library that's already > installed instead of the version you just compiled, and there is nothing > you can do to prevent it. You won't notice anything if all you ever do > is "make && make install", because the new library will replace the old, > but if you try to run your program directly from the build tree, it will > use the wrong library. This can be incredibly frustrating if you're not > aware of it - imagine you're trying to fix a bug in that library and no > matter what you do, your regression test keeps failing...
Are you talking about gcc implicitly searching /usr/local/include and /usr/local/lib? _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
