unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ian Grant <ian.a.n.grant@googlemail.com>
To: Mark H Weaver <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: guile-2.0.11 build: libtool and readline problems
Date: Mon, 21 Apr 2014 23:17:20 -0400	[thread overview]
Message-ID: <CAKFjmdyzBzzCrmeQNnXner7zbgkAey+QrEOmCq=g0+1Uqz-5nA@mail.gmail.com> (raw)
In-Reply-To: <CAKFjmdxs-GbEksOa3hN0qORL5uJabCRuY2ki2p4hgyfP+djCnw@mail.gmail.com>

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.grant@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.grant@googlemail.com> wrote:
>> On Mon, Apr 21, 2014 at 11:02 PM, Mark H Weaver <mhw@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



  parent reply	other threads:[~2014-04-22  3:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15  0:21 guile-2.0.11 build: libtool and readline problems Ian Grant
2014-04-15 14:07 ` Greg Troxel
2014-04-16  5:10 ` Mark H Weaver
2014-04-21 19:18   ` Ian Grant
2014-04-22  3:02     ` Mark H Weaver
     [not found]       ` <CAKFjmdw5n=5NXOswNowTCK1jNyRJW335wg+iagcFMYa=H3m6SA@mail.gmail.com>
     [not found]         ` <CAKFjmdxs-GbEksOa3hN0qORL5uJabCRuY2ki2p4hgyfP+djCnw@mail.gmail.com>
2014-04-22  3:17           ` Ian Grant [this message]
2014-04-22  3:33             ` Mark H Weaver
2014-04-22  3:29       ` Ian Grant
2014-04-22  1:16   ` Ian Grant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKFjmdyzBzzCrmeQNnXner7zbgkAey+QrEOmCq=g0+1Uqz-5nA@mail.gmail.com' \
    --to=ian.a.n.grant@googlemail.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).