From owner-freebsd-hackers@freebsd.org Fri Apr 21 03:07:12 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1A4FD48C97 for ; Fri, 21 Apr 2017 03:07:12 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id CA1141818; Fri, 21 Apr 2017 03:07:12 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id v3L37BVk001409 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 20 Apr 2017 20:07:11 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: How to get rid of the conflict between /usr/local/lib/gcc49/libgcc_s.so.1 and /lib/libgcc_s.so.1 To: Ian Lepore , Freebsd hackers list References: <2978fd74-4544-db57-f4f2-9300949e4764@rawbw.com> <1492707174.56859.1.camel@freebsd.org> From: Yuri Message-ID: <3d94b807-8ff4-42f9-59c0-bb3ee6026745@rawbw.com> Date: Thu, 20 Apr 2017 20:07:10 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1492707174.56859.1.camel@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 03:07:13 -0000 On 04/20/2017 09:52, Ian Lepore wrote: > A PR about this with lots more info and some potential fixes (or at > least workarounds) is: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120 208120 has some additional information, but for some reason it focuses on cmake when the problem is caused by the presence of multiple versions of libgcc. Users of fortran may or may not use cmake, therefore this problem is orthogonal to cmake. Yuri