Date: Wed, 8 Mar 2017 18:21:24 +0100 From: Tijl Coosemans <tijl@FreeBSD.org> To: Dag-Erling =?UTF-8?B?U23DuHJncmF2?= <des@des.no> Cc: Baptiste Daroussin <bapt@FreeBSD.org>, ports@FreeBSD.org, arch@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170308182124.79c4bc13@kalimero.tijl.coosemans.org> In-Reply-To: <86mvcvojzt.fsf@desk.des.no> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <86mvcvojzt.fsf@desk.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 08 Mar 2017 16:39:50 +0100 Dag-Erling Sm=C3=B8rgrav <des@des.no> wr= ote: > 4) Remove the hardcoded library path in lang/gcc* >=20 > 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170308182124.79c4bc13>