Re: libffi 3.3 release candidate 1

[Anthony Green <green@moxielogic.com>]

On Sat, Nov 9, 2019 at 11:04 AM Matthias Klose <doko@ubuntu.com> wrote:

> > The arm64 failures are mysterious runtime failures.  The libffi test
> > results for arm64 are good, so I'm wondering if the debian package adds
> any
> > patches.
>
> no patches.
>

I tested g-wrap (upstream) on arm64, and am not able to reproduce the
problem.  "make check" worked fine with the new libffi.


> The jffi failures all look like this:
> >
> >       [exec] make[2]: *** No rule to make target '-L/usr/lib/../lib',
> > needed by '/<<PKGBUILDDIR>>/build/jni/jffi/LongDouble.o'.  Stop.
> >
> > Perhaps this has something to do with how libffi is installed now?
> > Regardless, it's probably easy to fix whatever it is.
>
> libffi has in the pkg-config file: Libs: -L/usr/lib/../lib
> Normally pkg-config filters out system directories, but apparently fails
> for
> noncanonical paths.  And jffi only expects libs.  So something packagers
> should
> catch, unless you want to remove all the multilib build support, but I'm
> still
> awaiting your libffi merge for GCC 10 ;)
>

This may never happen.  libffi should probably just come out of GCC, and go
can depend on the system libffi.



> > The arm64 failures seem like a blocker for the release, which I'm still
> > hoping to get out on Nov 12.
>
> haskell-stack haskell-termonad are the remaining regressions, but I'm not
> sure
> if they are related at all.
>

They don't look like libffi issues to me.

AG