From owner-freebsd-ports@freebsd.org Mon Feb 25 01:58:17 2019 Return-Path: Delivered-To: freebsd-ports@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 597011516A8D for ; Mon, 25 Feb 2019 01:58:17 +0000 (UTC) (envelope-from dimpase@gmail.com) Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 465886C665; Mon, 25 Feb 2019 01:58:15 +0000 (UTC) (envelope-from dimpase@gmail.com) Received: by mail-lj1-x244.google.com with SMTP id j19so5998482ljg.5; Sun, 24 Feb 2019 17:58:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=RznpEa8bK6nEfHDgiZ78DUDr5PRRq9IQF/AfwzdVoNI=; b=qtLh6X+MCyQdXaOTKjiTxT+tIX74aJg+HJdtfz76H6CECScGjyUhmhjibdYiopi3cY s5DIkJ8W4nSTuH1XxpygRid00rZ2TNVxgAztu4dXFjrhE1yF4MbY7Fi3s4uzAFWy8kjC QMhycn742lmXBbpRzev+1qtv9QyUaPxT0B8oOWlb9bx1uvJpHgyidkhLEq/537sNPi8l /vxziwywUZ3vsMYbWLX6YNcYbUess6XyTai/Me9IQaJtjJVzo0q4Xqx4lpBMOvdnZYug /XRz+k7mPLUMYcwrhrAGsAAqrUmqTxX/cObOV5L7r9NjE91t+Cj2Zkh1n4heHSMyBOCa 8g8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=RznpEa8bK6nEfHDgiZ78DUDr5PRRq9IQF/AfwzdVoNI=; b=kjiaa7xJqm9XZ9D3LOezE3UOviNNPqpCBHn2U5SWTPeSyJ+CYDeZP9DTI4EIxWLRcf UgoRfGrqx57GBpGhTLQ3mnpYc5uax5YfCQBCn9EReKA1zThdF+lYRyxD0YyOwyBNDOQI exenuDRbNCMQBd99a835kv7xfWlG8zzbmiWBrlyBgpbtgYQsbIME5aW9ml0zFfZ1V8bW Fo66e0zZ2xD7fxIWZAKFwKx08D/nYdZh4QfKEa5b+T8S7hryytt4hTUKUCYWI13NQUsP ctYdhZYPf4mm77Lm+A/X24VtYbjbjVlNGX26G8S4F0D685bl6W2jZbCXLJe705TyCntE +S5A== X-Gm-Message-State: AHQUAuZLtbPVNq6O6wJyxRj+EMV2pdgqEzzvZVK69aw1luNIBFPPAqG2 /5bNmpppp3FQYKSh+iCj6JMzyKlg2hjPV8HndGA= X-Google-Smtp-Source: AHgI3Iamb1rOa1WWYw20pG+hSIZ+70T/moF6ww8ATMlvOc6xtbi/zLyZAsj5Me28OH05LCxi4pbuENmRZHvBlelZHZk= X-Received: by 2002:a2e:801:: with SMTP id 1mr3184448lji.61.1551059893598; Sun, 24 Feb 2019 17:58:13 -0800 (PST) MIME-Version: 1.0 References: <416689e6-37f9-17ec-54d8-0d224c26f30f@pinyon.org> <20190217151604.GB68620@night.db.net> <20190221180515.39c79ce6@kalimero.tijl.coosemans.org> <092b17f0-6fbf-662e-1061-403442248abd@pinyon.org> <20190222140407.2145c11e@kalimero.tijl.coosemans.org> <20190223000620.GA12700@troutmask.apl.washington.edu> <20190223183117.GA65065@night.db.net> <20190224142150.685debe4@kalimero.tijl.coosemans.org> <20190224200914.GA26706@troutmask.apl.washington.edu> In-Reply-To: <20190224200914.GA26706@troutmask.apl.washington.edu> From: Dima Pasechnik Date: Mon, 25 Feb 2019 01:58:01 +0000 Message-ID: Subject: Re: FreeCAD 0.17 && /lib//libgcc_s.so.1 To: Steve Kargl Cc: =?UTF-8?Q?T=C4=B3l_Coosemans?= , Diane Bruce , Dima Pasechnik , gerald@freebsd.org, Dave Horsfall , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 465886C665 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qtLh6X+M; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of dimpase@gmail.com designates 2a00:1450:4864:20::244 as permitted sender) smtp.mailfrom=dimpase@gmail.com X-Spamd-Result: default: False [-2.37 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_SEVEN(0.00)[7]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[freebsd]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.975,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.79)[0.785,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.17)[ip: (3.47), ipnet: 2a00:1450::/32(-2.25), asn: 15169(-2.00), country: US(-0.07)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2019 01:58:17 -0000 On Sun, Feb 24, 2019 at 8:09 PM Steve Kargl wrote: > > On Sun, Feb 24, 2019 at 02:21:50PM +0100, T=C4=B3l Coosemans wrote: > > On Sat, 23 Feb 2019 13:31:17 -0500 Diane Bruce wrote: > > > On Sat, Feb 23, 2019 at 10:52:03AM +0000, Dima Pasechnik wrote: > > >> On Sat, Feb 23, 2019 at 12:07 AM Steve Kargl > > >> wrote: > > >>> On Sat, Feb 23, 2019 at 09:19:01AM +1100, Dave Horsfall wrote: > > >>>> On Fri, 22 Feb 2019, T=C4=B3l Coosemans wrote: > > >>>>> If I were the lang/gcc maintainer this -rpath problem would be my > > >>>>> number one priority. The current maintainer has never proposed > > >>>>> any solutions and when I submit patches he always resists. I'm > > >>>>> done wasting my time fighting him. > > >>>> > > >>>> I'm late to this discussion (not being a Fortran/Python user) but > > >>>> is there any way to remove a recalcitrant maintainer? > > >>> > > >>> Can you explain what you mean? The maintainer of the lang/gcc > > >>> ports is a long-time member of the GCC steering committee > > >>> and a long-time maintainer of all gcc FreeBSD ports. There > > >>> are very few FreeBSD users (like 3 of us) who have commit access > > >>> to the gcc tree. Seems like a dubious idea to remove one of > > >>> those 3. > > >> > > >> Given the amount of time unsuspecting and half-suspecting users wast= ed > > >> on making Fortran code (often in form of a Python extension) working > > >> on FreeBSD (e.g. I probably wasted weeks), time is high to do > > >> something, e.g. commit the said patches---there is an agreement that > > >> they are correct, right? > > > > > > Dima, gerald has always been very helpful in all my communications > > > with him. Have you filed a PR for the fix? dropped him an email? > > > > > > I know we (gerald and ?? can't remember) tried a static lib change > > > a few years ago. I believe it didn't work at the time due to missing > > > symbols which we have since added. > > > > This cannot be entirely correct. I don't see what missing symbols this > > would have been. I attached my patch to bug 208120 on 2017-02-09 and > > you responded it was the best idea. mmel then discovered it didn't > > entirely fix the problem on ARM where _Unwind_Backtrace has version > > GCC_4.3.0 instead of GCC_3.3.0. The gcc commit that changed this > > doesn't explain why this was done, but we'll have to make the same > > change in FreeBSD ARM libgcc_s to be ABI compatible (since _Unwind* is > > part of the ABI). This isn't a blocker for the patch. > > > > I emailed the patch to gerald on 2017-02-21. He responded in the usual > > way that he prefers patches submitted upstream and because I thought th= e > > patch would not be accepted upstream he proposed an alternative solutio= n > > where gcc would always add -rpath on FreeBSD so you didn't have to > > specify it on the command line. I responded this wouldn't fix the case > > where clang was used as a linker (e.g. to combine fortran and c++ code > > in one program) and that the FAQ on the gcc website said it was a bad > > idea for other reasons. I also said upstream might accept my patch if > > it was a configure option but that the gcc configure scripts are > > complicated and I didn't know where to add it exactly. Then silence. > > This is typical for all my conversations with him over the years so I > > stopped caring. > > > > I do find the above paragraph to be somewhat ironic. It seems > that python importing Fortran compiled code runs into this > problem. I have sent 3 or 4 patches to freebsd-ports@, freebsd-python, > and created a PR to fix a conflict with the symbol sinpi (which I > intend to add to libm), and I have been told to upstream my patch. The patch ought to be upstream, for your patch is quite meaningful outside of FreeBSD ports. > > Well, I checked. I would need to create an account on a python > site to send a 2-line patch. GitHub is hardly a "python site" (or rather CPython, as we talk about - yes, you need to do a PR at their GitHub repo, which is totally standard practice nowadays. https://devguide.python.org/ OK, if you need someone to do such a PR on your behalf, surely this can be arranged. > Given that I actually don't > program in python, that certainly seems to be an unreasonable > request from the python maintainers. If I were a Python maintainer I might have pointed out to you that IEEE-754 speaks about sinPi(), not sinpi(), and if you added sinPi() to libm, it would have been fine without a patch. (although this might be breaking naming taboos :-)) Dima > > BTW, I am a gfortran maintainer. gfortran is the only Fortran > compiler available for FreeBSD that actually implements most > of the Fortran standards. I've spent 15+ years making sure > gfortran works on FreeBSD and that changes to GCC don't cause > regression. This is first time I've seen your patch. AFAICT, > the file libgfortran/Makefile.am needs a patch, and then a > around of automake, autoconf, aclocal needs to be done. Just > need to figure out what needs to change and ensure that it > does not break the rest of the computing world. > > -- > Steve