Date: Sun, 24 Mar 2019 07:03:11 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Sean Bruno <sbruno@freebsd.org> Cc: Dimitry Andric <dim@FreeBSD.org>, freebsd-ports@freebsd.org Subject: Re: Clang Import Breakage Message-ID: <woko-g674-wny@FreeBSD.org> In-Reply-To: <7772912d-0c87-a952-80ff-432f294644ed@freebsd.org> (Sean Bruno's message of "Sat, 23 Mar 2019 18:04:08 -0600") References: <393c9f59-6896-8ffc-6101-6d74e79eff4c@freebsd.org> <FAE3F56B-2296-4F2A-836C-0CC4D85F6258@FreeBSD.org> <7772912d-0c87-a952-80ff-432f294644ed@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean Bruno <sbruno@freebsd.org> writes: > On 3/23/19 5:57 PM, Dimitry Andric wrote: >> This is fallout of <https://svnweb.freebsd.org/changeset/base/345349>, >> which enabled --no-allow-shlib-undefined by default. See also >> <https://bugs.freebsd.org/236141>. Executive summary: lots of programs >> do not specify all their required libraries, a.k.a. "under-linking". >> >> I haven't yet reverted lld's new default, since it seems that a lot of >> under-linking fixes are now being made. These problems will also occur >> when linking with gold, for instance, so it is quite useful to solve >> them once and for all. >> >> -Dimitry > > Oh, hrm. Ok. > > So, before the changes, my port succeeds in adding libogg to its LD list > when doing its link. LLD before and BFD linker didn't complain that your port bootlegged libogg via libvorbis. For one, libvorbis may stop depending on libogg, may bundle libogg as a static library or import libogg symbols with LOCAL visibility. Ditto for libssl bootlegging libcrypto.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?woko-g674-wny>