And now I remember why I did this: it was because this web site, which is the official site for libffi, has a bad SSL certificate. (sec_error_untrusted_issuer)
http://sourceware.org/libffi/ It's not good for guile to rely on third party source like this: I have the same reservations about the garbage collector. What can we do about that? One solution would be to try to get the maintainers of these libraries to make them proper GNU software, but perhaps that would be difficult, or impossible legally. On Mon, Apr 21, 2014 at 11:10 PM, Ian Grant <ian.a.n.gr...@googlemail.com> wrote: > It's because I had to build libffi from the git repo, and I 4cked up > the auto4ck stuff that one has to do in this situation. I will try > and get a proper distribution .... > > On Mon, Apr 21, 2014 at 11:07 PM, Ian Grant > <ian.a.n.gr...@googlemail.com> wrote: >> On Mon, Apr 21, 2014 at 11:02 PM, Mark H Weaver <m...@netris.org> wrote: >>> Hi Ian, >>> >>> Three questions: >>> >>> 1. What is the output of "pkg-config --libs libffi" on your system? >> >> -L\$\(libdir\) -lffi >> >> Bingo! Good question :-) >> >>> 2. What is the output of "grep '^LIBFFI' libguile/Makefile"? >> >> LIBFFI_CFLAGS = -I/usr/local/lib/libffi-3.0.14-rc0/include >> LIBFFI_LIBS = -L\$\(libdir\) -lffi >> >>> 3. What is the output of "grep '^READLINE_LIBS' libguile/Makefile"? >> >> READLINE_LIBS = -L/usr/local/lib -lreadline -R/usr/local/lib -lncurses >> >>> Thanks, >>> Mark