Thanks. Indeed, libffi is alive and well:
...
checking for ffi_closure_alloc in -lffi... yes
checking ffi/ffi.h usability... no
checking ffi/ffi.h presence... no
checking for ffi/ffi.h... no
checking ffi.h usability... yes
checking ffi.h presence... yes
checking for ffi.h... yes
checking whether we can use the existing libffi library ... yes
...
;;; gcc -o libecl.so
-L/usr/local/sage/sage-9.3/local/var/tmp/sage/build/ecl-21.2.1/src/build/
c/main.o c/all_symbols2.o liblsp.a libeclmin.a
-Wl,--rpath,/usr/local/sage/sage-9.3/local/lib/ -shared
-Wl,-rpath-link,/usr/local/sage/sage-9.3/local/lib
-L/usr/local/sage/sage-9.3/local/lib
-Wl,-rpath,/usr/local/sage/sage-9.3/local/lib
-Wl,-rpath-link,/usr/local/sage/sage-9.3/local/lib
-L/usr/local/sage/sage-9.3/local/lib
-Wl,-rpath,/usr/local/sage/sage-9.3/local/lib
-Wl,-soname,libecl.so.21.2 -lgmp -lgc -lffi -lgc -ldl -lm
Comparing with the failed call
Error code 1 when executing
(EXT:RUN-PROGRAM "gcc" ("-o" "binary-ecl/maxima-package.fas"
"-L/usr/local/sage/sage-9.3/local/lib/" "/tmp/eclinit0kBo2G.o"
"binary-ecl/maxima-package.o"
"-Wl,--rpath,/usr/local/sage/sage-9.3/local/lib/" "-shared"
"-Wl,-rpath-link,/usr/local/sage/sage-9.3/local/lib" "-L/usr
/local/sage/sage-9.3/local/lib"
"-Wl,-rpath,/usr/local/sage/sage-9.3/local/lib"
"-Wl,-rpath-link,/usr/local/sage/sage-9.3/local/lib"
"-L/usr/local/sage/sage-9.3/local/lib"
"-Wl,-rpath,/usr/local/sage/sage-9.3/local/lib" "-lecl" "-lgmp" "-lgc"
...)):
/usr/bin/ld: cannot find -lffi
does not seem to reveal anything interesting.
On Fri, May 14, 2021 at 1:46 PM John Cremona <john.crem...@gmail.com> wrote:
>
> Here is the ECL log.
>
> John
>
> On Fri, 14 May 2021 at 13:20, Michael Orlitzky <mich...@orlitzky.com> wrote:
> >
> > On Fri, 2021-05-14 at 12:12 +0100, Dima Pasechnik wrote:
> > > >
> > > > The other possibility is that the linker is told not to look for
> > > > system-wide libffi - can this be achieved with -L and -Wl,-rpath ?
> > > >
> > > > On the other hand, it's a bug in maxima, which does not try to check
> > > > for presense of libffi, just assumes it's there.
> > >
> > > oops, I meant to say, it's a bug in ECL, as this failing call to gcc
> > > is emitted by ECL.
> > >
> >
> > I ran into a problem recently that sounds relevant:
> >
> > https://sourceforge.net/p/maxima/bugs/3759/
> >
> > I wonder how hard it would be at this point to teach Sage to use the
> > system copy of Maxima. That will be the long-term solution anyway.
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to sage-devel+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/sage-devel/e53fd6c259f8bd2284938c2627f8902c07af455e.camel%40orlitzky.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAD0p0K5B2t%3DLiwJ0j%2Bm_RtrTyy%2BNvpD414ACYkOrNr3dxk7qww%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0YkNC4aPkqHaUui%2BYzG1aDNVoFYou%3DWu7Vr3uWG98xVg%40mail.gmail.com.
