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> In-Reply-To: <20180510202536.GA74173@troutmask.apl.washington.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180510210157.GA17726>