From: Mark H Weaver <mhw@netris.org>
To: Ian Grant <ian.a.n.grant@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: guile-2.0.11 build: libtool and readline problems
Date: Wed, 16 Apr 2014 01:10:00 -0400 [thread overview]
Message-ID: <87wqepdfmf.fsf@yeeloong.lan> (raw)
In-Reply-To: <CAKFjmdxufT=nYoZmyOoa2ZUTqBJh972JJbsks7pNFRWoej21PA@mail.gmail.com> (Ian Grant's message of "Mon, 14 Apr 2014 20:21:13 -0400")
Hi,
Ian Grant <ian.a.n.grant@googlemail.com> 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 "libguile-@GUILE_EFFECTIVE_VERSION@.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
next prev parent reply other threads:[~2014-04-16 5:10 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 [this message]
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
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=87wqepdfmf.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ian.a.n.grant@googlemail.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).