From owner-freebsd-hackers@freebsd.org Thu May 10 19:05:59 2018 Return-Path: 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 DC76EFD3A04 for ; Thu, 10 May 2018 19:05:59 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (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 67ABE841F4 for ; Thu, 10 May 2018 19:05:58 +0000 (UTC) (envelope-from joerg@bec.de) X-Originating-IP: 87.153.197.147 Received: from britannica.bec.de (p5799C593.dip0.t-ipconnect.de [87.153.197.147]) (Authenticated sender: joerg@bec.de) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 11F0F1C0006 for ; Thu, 10 May 2018 21:05:53 +0200 (CEST) Date: Thu, 10 May 2018 21:05:49 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: Runtime loader issue Message-ID: <20180510190549.GB14916@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20180509234551.GA39526@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180509234551.GA39526@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 19:06:00 -0000 On Wed, May 09, 2018 at 04:45:51PM -0700, Steve Kargl wrote: > In review PR 228007, it came to my attention some individuals are > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > issue". I don't get why you are blaming the FreeBSD loader. In fact, this is a pretty common issue and the fault is and has always been that the GCC ecosystem is extremely bad about mixing different GCC versions in the runtime environment. It tends to somewhat work as long as you make sure that the main binary is using the newest GCC version, but it can still fail even then. Joerg