From owner-freebsd-hackers@freebsd.org  Thu May 10 21:02:08 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@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 399F3FD70EB
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Thu, 10 May 2018 21:02:08 +0000 (UTC) (envelope-from joerg@bec.de)
Received: from relay12.mail.gandi.net (relay12.mail.gandi.net [217.70.178.232])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B899A7F4F7
 for <freebsd-hackers@freebsd.org>; Thu, 10 May 2018 21:02:07 +0000 (UTC)
 (envelope-from joerg@bec.de)
Received: from britannica.bec.de (p5799C593.dip0.t-ipconnect.de
 [87.153.197.147]) (Authenticated sender: joerg@bec.de)
 by relay12.mail.gandi.net (Postfix) with ESMTPSA id 400A720000F
 for <freebsd-hackers@freebsd.org>; Thu, 10 May 2018 23:02:00 +0200 (CEST)
Date: Thu, 10 May 2018 23:01:57 +0200
From: Joerg Sonnenberger <joerg@bec.de>
To: freebsd-hackers@freebsd.org
Subject: Re: Runtime loader issue
Message-ID: <20180510210157.GA17726@britannica.bec.de>
Mail-Followup-To: freebsd-hackers@freebsd.org
References: <20180509234551.GA39526@troutmask.apl.washington.edu>
 <20180510190549.GB14916@britannica.bec.de>
 <20180510194823.GA60567@troutmask.apl.washington.edu>
 <20180510202227.GA6592@britannica.bec.de>
 <20180510202536.GA74173@troutmask.apl.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180510202536.GA74173@troutmask.apl.washington.edu>
User-Agent: Mutt/1.9.5 (2018-04-13)
X-Spam-Level: 
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 21:02:08 -0000

On Thu, May 10, 2018 at 01:25:36PM -0700, Steve Kargl wrote:
> On Thu, May 10, 2018 at 10:22:27PM +0200, Joerg Sonnenberger wrote:
> > 
> > Again, you are missing that the situation would happen just the same if
> > the base compiler is GCC 4.2.1 and not Clang. 
> > 
> 
> FreeBSD could have stayed in-step with the times.

FreeBSD or any other system could be updated the GCC version for every
release and there would still appear a newer GCC version that requires
an even newer libgcc_s.so in the release life time. Heck, the very same
problem happens in the other direction as well, i.e. if you are forced
to use an *older* GCC and pick up its libgcc_s.so.

Joerg