unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
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: Tue, 15 Apr 2014 10:07:06 -0400	[thread overview]
Message-ID: <rmir44yy9dh.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <CAKFjmdxufT=nYoZmyOoa2ZUTqBJh972JJbsks7pNFRWoej21PA@mail.gmail.com> (Ian Grant's message of "Mon, 14 Apr 2014 20:21:13 -0400")

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]


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
>
> [.... 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
>
> 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.

You should not have to set libdir when you set prefix.

I am unclear on --wtih-libreadline-prefix, but generally in the autoconf
world when prereqs are not in the standard search path, I invoke

  CPPFLAGS="-I/usr/pkg/include" \
  LDFLAGS="-L/usr/pkg/lib -R/usr/pkg/lib" \
  ./configure ....

So you may want to try that.  Another thing to do is to read config.log
to see what configure is doing.  It seems obvious that
--with-libreadline-prefix=/usr/local should cause the equivalent
CPPFLAGS/LDFLAGS to be used when looking for readline, and if found, to
be added, but perhaps something is amiss there.

[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]

  reply	other threads:[~2014-04-15 14:07 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 [this message]
2014-04-16  5:10 ` Mark H Weaver
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=rmir44yy9dh.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --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).