guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile-2.0.11 build: libtool and readline problems


From: Mark H Weaver
Subject: Re: guile-2.0.11 build: libtool and readline problems
Date: Wed, 16 Apr 2014 01:10:00 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Hi,

Ian Grant <address@hidden> writes:

> I'm at a loss. I have libtool-2.4 installed in /usr/local and I get
> this error when 'make'ing after running
>
> ../configure --prefix=/usr/local --libdir=/usr/local/lib \
> --with-libreadline-prefix=/usr/local

FWIW, you could leave out the "--libdir=/usr/local/lib" above, since
that would be the default anyway, but I'm still curious what's going
wrong here.

>
> [.... making lots of stuff ...]
>
> CCLD libguile-2.0.la
> ../libtool: line 5989: cd: (libdir): No such file or directory
> libtool: link: cannot determine absolute directory name of `(libdir)'
> make[3]: *** [libguile-2.0.la] Error 1
> make[3]: Leaving directory
> `/home/ian/Documents/FP/guile-2.0.11/build/libguile'
> make[2]: *** [all] Error 2

Can you try "make V=1" and show us the output that corresponds to
the above?

The relevant rule starts with "address@hidden@.la:"
in libguile/Makefile.in (line 2241 in guile-2.0.11).  In the generated
libguile/Makefile, the relevant rule starts with "libguile-2.0.la:".

I see "-rpath $(libdir)" in the associated command, but it seems as if a
bare "(libdir)" is getting passed to libtool somehow.

What kind of system are you doing this on?  What version of make?

> Another minor issue is that the configure script seems not to know
> about the readline-6.3 which I have installed in /usr/local:
>
> checking for rl_get_keymap... no
> checking for rl_getc_function pointer in readline... no
> configure: WARNING: *** GNU Readline is too old on your system.
> configure: WARNING: *** You need readline version 2.1 or later.

Can you search for "rl_get_keymap" in "config.log" and see what went
wrong here?  It tries to compile a simple test program, and it would be
useful to see what error message(s) it printed.

You probably already know this, but on a GNU/Linux system it's important
to run "ldconfig" as root after installing libraries from source code.

    Regards,
      Mark



reply via email to

[Prev in Thread] Current Thread [Next in Thread]