Re: Bug#897416: mpfr4: FTBFS on kfreebsd-amd64
On Thu, 2018-05-03 at 14:59 +0100, James Clarke wrote:
> On 3 May 2018, at 09:21, Svante Signell <email@example.com>
> > On Wed, 2018-05-02 at 12:51 +0100, James Clarke wrote:
> > > Control: reassign -1 gcc-7
> > > Control: retitle -1 gcc: Decimal float support is not enabled on
> > > kfreebsd-
> > > amd64
> > >
> > > On 2 May 2018, at 10:38, Svante Signell <firstname.lastname@example.org
> > > > wrote:
> > > >
> > > > Source: mpfr4
> > > > Version: 4.0.1-1
> > > > Severity: important
> > > > Tags: patch
> > > > User: email@example.com
> > > > Usertags: kfreebsd
> > I think it is unfortunate that you reassigned this bug to gcc-7.
> > That will not
> > solve the mpfr4 build on the buildds.
> > There are two ways to solve this problem:
> > 1)
> > - reassign this bug back to mpfr4, adding the
> > libfr6.symbols.kfreebsd-amd64 in
> > next version 4.0.1-2.
> Well, if you wanted to do that, it should be by changing the
> (arch=...) restriction lists in the main libfr6.symbols rather than
> forking a copy for kfreebsd-amd64.
Do you mean changing
(arch=any-amd64 any-i386 powerpc ppc64 ppc64el s390x)mpfr_get_decimal64
(arch=any-amd64 !kfreebsd-amd64 any-i386 powerpc ppc64 ppc64el s390x)mp
if that works. Or list all arch-any architectures except kfreebsd-
amd64. How to find the architecture list for any-amd64?
The result would still be the same: as soon as gcc-7-7.3.0-18 is built
the libfr6.symbols file has to be changed again. Wouldn't it be better
to just remove the libfr6.symbols.kfreebsd-amd64 file for next version
of mpfr4 4.0.1-2?
> > - clone this bug to gcc-7, adding a patch to dfp.m4 so it can be
> > integrated in
> > next release of gcc-7: 7.3.0-18?
> Personally I'd just get gcc patched and give back mpfr4.
How would you be able to build gcc-7 on the buildds with the current
mpfr4-4.0.1-1? It does not build as is on kfreebsd-amd64.