unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel Development <guile-devel@gnu.org>
Subject: Re: One config issue solved, only to trip over another.
Date: Mon, 28 Feb 2011 11:58:10 -0800	[thread overview]
Message-ID: <AANLkTiniFAdraQZzsKZ6v2YdZ7x5_K+rXasKSGSmiQtV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi==S1dbBw+kZFTB+bLOLfZv7+BGvgLXbDCzQFFB@mail.gmail.com>

Hi,

On Mon, Feb 28, 2011 at 11:25 AM, Noah Lavine <noah.b.lavine@gmail.com> wrote:
> Hello,
>
> I think the list you want is in Guile's README file, which says that
> Guile depends on these libraries:

More or less.

> - libgmp
OK

> - libiconv
Not available for openSuSE

> - libintl
A perl library?

> - libltdl
> - libunistring
> - libgc
OK

> - libffi

It's installed.  The configure script doesn't detect it.  It was installed
via Yast from the openSuSE site, so I would hope the sentence,
"Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix." does not apply.

$ find /usr/lib* /usr/local/lib* -name 'libffi.*'
/usr/lib/libffi.so.4.0.1
/usr/lib/debug/usr/lib64/libffi.so.4.0.1.debug
/usr/lib/libffi.so
/usr/lib/libffi.so.4
/usr/lib/libffi.a
/usr/lib64/libffi.so.4.0.1
/usr/lib64/libffi.so
/usr/lib64/libffi.so.4
/usr/lib64/libffi.a



  reply	other threads:[~2011-02-28 19:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 18:43 One config issue solved, only to trip over another Mike Gran
2011-02-28 19:13 ` Bruce Korb
2011-02-28 19:25   ` Noah Lavine
2011-02-28 19:58     ` Bruce Korb [this message]
2011-02-28 20:38       ` Andreas Rottmann
2011-02-28 22:26 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2011-02-28 18:14 Bruce Korb

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=AANLkTiniFAdraQZzsKZ6v2YdZ7x5_K+rXasKSGSmiQtV@mail.gmail.com \
    --to=bruce.korb@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    /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).