From owner-freebsd-ports@freebsd.org  Sun Mar 24 06:03:15 2019
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC03C154BC19
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sun, 24 Mar 2019 06:03:14 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 887CA6DD78;
 Sun, 24 Mar 2019 06:03:14 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id 76046EE27; Sun, 24 Mar 2019 06:03:14 +0000 (UTC)
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
References: <393c9f59-6896-8ffc-6101-6d74e79eff4c@freebsd.org>
 <FAE3F56B-2296-4F2A-836C-0CC4D85F6258@FreeBSD.org>
 <7772912d-0c87-a952-80ff-432f294644ed@freebsd.org>
Date: Sun, 24 Mar 2019 07:03:11 +0100
In-Reply-To: <7772912d-0c87-a952-80ff-432f294644ed@freebsd.org> (Sean Bruno's
 message of "Sat, 23 Mar 2019 18:04:08 -0600")
Message-ID: <woko-g674-wny@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain
X-Rspamd-Queue-Id: 887CA6DD78
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.90 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-1.00)[-0.998,0];
 NEURAL_HAM_LONG(-1.00)[-0.999,0];
 NEURAL_HAM_SHORT(-0.91)[-0.906,0];
 ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2019 06:03:15 -0000

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.