Re: Can not work with libguile-2.0

[Andy Wingo <wingo@pobox.com>]

Hi Mark,

On Fri 18 Feb 2011 20:42, Mark Harig <idirectscm@aim.com> writes:

>     gcc -I /usr/local/include/guile/2.0 -shared \
>         -o libguile-bessel.so -fPIC bessel.c
>
> Then, the problem is to provide clear explanatory text on
> how the user can determine what value to provide to the '-I'
> switch.

I agree that we should be using pkg-config; I was just objecting to
adding --libs.

>> > In addition, the manual should mention that the environment
>> > variable 'PKG_CONFIG_PATH' needs to be set before invoking the
>> > compiler.  Something like the following needs to be added, along 
> with
>> > some explanatory text:
>> >
>> >  $ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
>>
>> Well that isn't quite right, as /usr/local/lib isn't the right place 
> for
>> libguile-2.0 on many systems.  It's lib64 on my fedora machine.
>>
>
> It's interesting that Guile installed libguile-2.0 in
> /usr/local/lib64 on your system.

That's not quite it; the default libdir is still $prefix/lib.  But on
Fedora systems, "lib" is for 32-bit libs, and "lib64" is for 64-bit
libs.  If you install a library into "lib" you will then end up having
to add the 32-bit libdir to your -L path, which is a path to madness.

What I'm saying is that if we make assumptions about where Guile goes,
we need to be explicit about them in the manual.

Cheers,

Andy
-- 
http://wingolog.org/