unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Paul Emsley <pemsley@mrc-lmb.cam.ac.uk>
To: 24219@debbugs.gnu.org
Subject: bug#24219: Fwd: Compiling guile-2.0.12
Date: Sat, 13 Aug 2016 15:10:21 +0100	[thread overview]
Message-ID: <1c2f80e3-387e-4484-cc53-e7e78a0ac4cd@mrc-lmb.cam.ac.uk> (raw)
In-Reply-To: <ddea10ff-53a2-ea1d-29a5-788ac3e92fae@mrc-lmb.cam.ac.uk>


Fwd at the request of Mark Weaver.

Paul


-------- Forwarded Message --------
Subject: Compiling guile-2.0.12
Date: Thu, 11 Aug 2016 22:26:25 +0100
From: Paul Emsley <pemsley@mrc-lmb.cam.ac.uk>
To: guile-user@gnu.org


$ ./configure --prefix=$HOME/guile-2 --with-libltdl-prefix=$HOME/guile-2

checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for libltdl... no
configure: error: GNU libltdl (Libtool) not found, see README.


config.log has this:

configure:46406: checking for libltdl
configure:46428: gcc -o conftest -g -O2   conftest.c  -lltdl >&5
conftest.c:598:18: error: ltdl.h: No such file or directory
configure:46428: $? = 1

It seems to me that the argument to --with-libltdl-prefix is not being 
checked.  And that seems like a bug.

Do you agree?

Paul.






       reply	other threads:[~2016-08-13 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ddea10ff-53a2-ea1d-29a5-788ac3e92fae@mrc-lmb.cam.ac.uk>
2016-08-13 14:10 ` Paul Emsley [this message]
2017-03-01  9:04   ` bug#24219: Fwd: Compiling guile-2.0.12 Andy Wingo

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=1c2f80e3-387e-4484-cc53-e7e78a0ac4cd@mrc-lmb.cam.ac.uk \
    --to=pemsley@mrc-lmb.cam.ac.uk \
    --cc=24219@debbugs.gnu.org \
    /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).