From owner-freebsd-hackers@freebsd.org Fri May 11 06:04:52 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 E8074FB873A for ; Fri, 11 May 2018 06:04:51 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 638D87C34D for ; Fri, 11 May 2018 06:04:51 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: by mail-pf0-x241.google.com with SMTP id p12-v6so2202374pff.13 for ; Thu, 10 May 2018 23:04:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:date:message-id:subject :in-reply-to:references:to; bh=+aoQRmj22lRw2pvJI41bNEHZRG3WxEsDK8nmBG0oRkk=; b=NqeHrKs2Ko5WSubKipLX+o5GIDRPYhsqzUpvItofWDiW0qxz50O/uYPjB3bGEPz+Ah EAa+H0Sv6GeGyHCt4ufyHW3IQ2H4100kZFo03Bm6f+YZiNNyNa0Aa5pdezc6YgrnDFkm LUXai2aGKtmaR4n0ogwvctgilFV7AuAJkwhpW6VzF8QrCcidaBxKqoA5OycJVmGj+WOC fONsSlAyyslokpLkrBlkRj5xaBKIe7s1YABapC5n0l2IaD5RlrXuv8ANuWTcBk4fiqo6 pP7hTGwzpHrFC/8JK3OWzROZZuz6c92fp6iC6N2lML7Mshd6uQ1u36YNc1WezoHm43Yb ZE1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version:date :message-id:subject:in-reply-to:references:to; bh=+aoQRmj22lRw2pvJI41bNEHZRG3WxEsDK8nmBG0oRkk=; b=mXwxrFiDSbbD4q1GVJq3isxyDlTaHs1VsgPF/SdALgDLsIXGyfpVlIlJAVomkG06Mg p1NUomOssoL/2ptQ7ODXqT0wdrq3gVFPpF9FDkOYNIZh5tQ2zKmG1udZ/pAL5e4g7N+w uJN1X3N2eVPc9HZhAtGRT8s8c5Eo+VJ2jaqjdb/3H2UIB6pgfVjZ+BCwGYlExEF6axIb 6sf5dDoR+TEFQInPBFURq+pC6SuPFbIxAlKbYvBJanIqvC9xpRT3UnqdoGKmWbt+y06U DjvRYtZn2HoZ9O5Lra7xQPgQrNUW0yh4tghdSZvoAONMaBjFTIMq4aycL/ubl45IagJb ccJw== X-Gm-Message-State: ALKqPwdwigjvvPycbv9pyTKlxW6v1s7jvWoJOxv9JqNGEFwHrteN/3C6 e41DstBVmWshe05eMkLF5ZYHYQqk X-Google-Smtp-Source: AB8JxZqMd9VjRH0JlmGcFpy5SyBz54UtS6Q6Fdn1MJOBC2/dzAh946paHznoS3JUPgIXxMxYYO6H8A== X-Received: by 2002:a63:8ac4:: with SMTP id y187-v6mr3387086pgd.64.1526018690069; Thu, 10 May 2018 23:04:50 -0700 (PDT) Received: from ?IPv6:2601:602:9701:71cb:3972:c74e:759c:7871? ([2601:602:9701:71cb:3972:c74e:759c:7871]) by smtp.gmail.com with ESMTPSA id a23-v6sm4214689pfi.176.2018.05.10.23.04.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 23:04:49 -0700 (PDT) From: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= Mime-Version: 1.0 (1.0) Date: Thu, 10 May 2018 23:04:48 -0700 Message-Id: <73A0769A-AAE0-4B23-83CA-206FA7EF0B5E@gmail.com> Subject: Re: Runtime loader issue In-Reply-To: <20180510210157.GA17726@britannica.bec.de> 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> <20180510210157.GA17726@britannica.bec.de> To: freebsd-hackers@freebsd.org X-Mailer: iPhone Mail (15E302) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 11 May 2018 06:04:52 -0000 > On May 10, 2018, at 2:01 PM, Joerg Sonnenberger wrote: >=20 >> 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: >>>=20 >>> Again, you are missing that the situation would happen just the same if >>> the base compiler is GCC 4.2.1 and not Clang.=20 >>=20 >> FreeBSD could have stayed in-step with the times. >=20 > 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. Hi. This libgcc issue is a little recurrent here in FreeBSD. I remember other em= ail threads talking about it. The summary I remember is that we must go the w= ay Linux does it, I think. It was thoroughly explained in past threads. As GCC was/is omnipresent in Unix like systems most of the other projects ha= ve standard ways to use the libgcc. I used to think in new libgcc as a drop i= n replacement for older ones. I know this is a bit simplistic. I remember Li= nux usually uses just one libgcc at a time, too. This is the winning answer u= sually here, too. In fact I remember that new libgcc versions triggers syste= ms recompilations for safety reasons. The use of libgcc in FreeBSD makes the procedure unusually complex many time= s here. It's a source of many problems. This one is one more to add to the l= ist. This just occurred to me now. Please, keep in mind that the case here i= s caused by the odd use given to this library here. Lc --=20 rollingbits =E2=80=94 =F0=9F=93=A7 rollingbits@gmail.com =F0=9F=93=A7 rollin= gbits@terra.com.br =F0=9F=93=A7 rollingbits@yahoo.com =F0=9F=93=A7 rollingbi= ts@globo.com =F0=9F=93=A7 rollingbits@icloud.com