Date: Wed, 08 May 2019 17:21:27 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 237688] lang/gcc8 fails to build: /usr/local/bin/ld: /wrkdirs/usr/ports/lang/gcc8/work/.build/./gcc/liblto_plugin.so: error loading plugin: Service unavailable Message-ID: <bug-237688-29464-iATSwlrx8L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237688-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-237688-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237688 --- Comment #8 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Gerald Pfeifer from comment #5) > So, it was a non-default setting after all. ;-) >=20 > That said, is there a better way of reasonably handling this within our > ports framework? Something like >=20 > .if $(binutils built statically) > IGNORE=3D GCC requires dynamically linked binutils > .endif Something like that, or somehow disable LTO plugins when building gcc, or at least warning about it. > Or perhaps drop the STATIC option from devel/binutils? Is this an=20 > important one for users? I think this option mirrors what we have in the base system, where for apparently historical reasons, most toolchain components (cc, ld, etc) are built statically. Most likely, the idea was to be able to get yourself out = of certain situations where the system is messed up, and then being able to rebuild it. It was added in ports r434650 by bdrewery, maybe he remembers what it was m= eant for? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237688-29464-iATSwlrx8L>