Date: Fri, 28 Dec 2012 19:57:22 -0800 (PST) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: freebsd-ports@freebsd.org Subject: Re: lang/gcc46 Message-ID: <1356753442.39132.YahooMailClassic@web164005.mail.gq1.yahoo.com> In-Reply-To: <alpine.LNX.2.00.1212281228180.4452@tuna.site>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry for the formatting. Reply is below --- On Fri, 12/28/12, Gerald Pfeifer <gerald@pfeifer.com> wrote: From: Gerald Pfeifer <gerald@pfeifer.com> Subject: Re: lang/gcc46 To: "Brendan Fabeny" <bf1783@gmail.com>, "Baptiste Daroussin" <bapt@FreeBSD= .org> Cc: freebsd-ports@freebsd.org, "Kevin Oberman" <kob6558@gmail.com> Date: Friday, December 28, 2012, 4:08 PM On Mon, 6 Aug 2012, b. f. wrote: > Oops: I forgot though, that partly due to this policy of not bumping > gcc shared library versions, we have some shared libraries in the base > system that conflict with the shared libraries of the various gcc > ports, and we have been enforcing the right links by inscribing hints > in the binaries to look first in the right gcc port directories.=A0 But > if we update lang/gcc from 4.6.x to another major version (e.g. > 4.7.x), the directory changes, and linking for the old binaries will > fail.=A0 So let me qualify my earlier answer: you can keep the old > software working with minimal intervention, for example, by adding a > symlink from the old directory to the new one. What we could do, for the canonical version of GCC (lang/gcc, USE_GCC=3Dyes) is install those libraries into /usr/local/lib instead of /usr/local/lib/gccXY as we are doing for lang/gccXY. What do you think? >>> I had patches to do this even without pkgng, but it made things a=20 >>> little more complicated, and didn't seem to be a high priority, so I=20 >>> didn't pursue it.=A0 If people feel that it is important, I could work= =20 >>> with Gerald to revive that >> Making this change now would benefit a lot of people, now. > Okay, but since I'm not in charge either, it will require (at least) > Gerald's consent. That would be cool.=A0 Bapt wanted to look into this as well a few months ago, so perhaps the two of you can (should?) sync before proceeding? Gerald PS: I don't think we should go for the other option, static linking. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" ..not=A0 a reply but additional information, I hope it is not to off-topic = to this post.=A0 While trying to install gcc46, it wanted gcc46 already ins= talled for some reason.=A0 I had just deleted it "for" the install.=A0 I di= d a workaround of sorts...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1356753442.39132.YahooMailClassic>