One config issue solved, only to trip over another.

One config issue solved, only to trip over another.

[Bruce Korb]

I was trying to build Guile 2.0, but I stubbed my toe on
"Oh, you haven't installed libunistring".  So, I found one
and installed  it:

checking for LIBFFI... configure: error: Package requirements (libffi) were not met:

No package 'libffi' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you

Which is precisely why I don't like building packages and prefer
to rely on distributions.  Someone else has already chased through
all the cascading dependencies.  I've googled for "guile 2.0 dependencies"
and meandered the software/guile pages, but the build prerequisites are
not clearly laid out.

Here is my project's pre-release:
  http://autogen.sourceforge.net/data/
It depends on Guile and a Bourne shell, though preferably bash.
"gperf" and "libxml2" are also nice, but not required.
I think it works with Guile 2.0 now, but I cannot test it.  :(

Re: One config issue solved, only to trip over another.

[Mike Gran]

> From:Bruce Korb <bruce.korb@gmail.com>
> 
> I was trying to build Guile 2.0, but I stubbed my toe on
> "Oh, you haven't installed libunistring".  So, I found one
> and installed  it:

> 
> checking for LIBFFI... configure: error: Package requirements (libffi) were not 
> met:

Really these checks should be at the top of the configure script.
On Cygwin where it takes about 10 minutes to do the configure,
it is a bit frustrating that these likely-to-fail checks are last.

Also, is the libunistring dependency still necessary, since
Guile's moved to its own iconv-based conversion?  If there are
only a few libunistring functions left, maybe we should try to
get rid of them or use gnulib for the rest.

> 
> No package 'libffi' found

On Fedora at least, libffi's been packaged for a long time.  I think
it is widely available generally as a pre-built package.

-Mike

Re: One config issue solved, only to trip over another.

[Bruce Korb]

Thanks, Mike,  but:

On Mon, Feb 28, 2011 at 10:43 AM, Mike Gran <spk121@yahoo.com> wrote:
>> No package 'libffi' found
>
> On Fedora at least, libffi's been packaged for a long time.  I think
> it is widely available generally as a pre-built package.

Saying that if you use Linux, then it must be Red Hat wouldn't fly far.....

I happen to use OpenSuSE, but the real problem is that I don't have
a list that I can just say, "go fetch and install these".  Tripping over
first one, then the next, then how many more?  I know I weary easily,
but I've stubbed my toe several times in succession before only to
finally download a package that doesn't build at all.  So I just don't
do it any more.  :(

I'm spoiled.  Stuff needs to be completely straight forward.

Re: One config issue solved, only to trip over another.

[Noah Lavine]

Hello,

I think the list you want is in Guile's README file, which says that
Guile depends on these libraries:

- libgmp
- libiconv
- libintl
- libltdl
- libunistring
- libgc
- libffi

Unless of course I misunderstood your question.

Noah

On Mon, Feb 28, 2011 at 2:13 PM, Bruce Korb <bruce.korb@gmail.com> wrote:
> Thanks, Mike,  but:
>
> On Mon, Feb 28, 2011 at 10:43 AM, Mike Gran <spk121@yahoo.com> wrote:
>>> No package 'libffi' found
>>
>> On Fedora at least, libffi's been packaged for a long time.  I think
>> it is widely available generally as a pre-built package.
>
> Saying that if you use Linux, then it must be Red Hat wouldn't fly far.....
>
> I happen to use OpenSuSE, but the real problem is that I don't have
> a list that I can just say, "go fetch and install these".  Tripping over
> first one, then the next, then how many more?  I know I weary easily,
> but I've stubbed my toe several times in succession before only to
> finally download a package that doesn't build at all.  So I just don't
> do it any more.  :(
>
> I'm spoiled.  Stuff needs to be completely straight forward.
>
>

Re: One config issue solved, only to trip over another.

[Bruce Korb]

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

Re: One config issue solved, only to trip over another.

[Andreas Rottmann]

Bruce Korb <bruce.korb@gmail.com> writes:

> 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:
>
>> - libiconv
> Not available for openSuSE
>
>> - libintl
> A perl library?
>
I think both of these are part of glibc (the latter being the gettext
interface), so if you are on a GNU system (which OpenSuSE presumably is
;-)), you should be fine. On the *BSDs, I think you need to actually
install these as separate systems.

>> - 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
>
File a bug with OpenSuSE, /usr/lib/pkgconfig/libffi.pc should be
contained in the same package as the .so and .a files; apparently their
package is incomplete.

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>

Re: One config issue solved, only to trip over another.

[Ludovic Courtès]

Hi,

Mike Gran <spk121@yahoo.com> writes:

> Also, is the libunistring dependency still necessary,

Yes, e.g., in scm_from_stringn.  Besides we may eventually provide
bindings for other parts of libunistring, like ‘unicode_character_name’,
etc.

Thanks,
Ludo’.