From: "Stewart, Adam James" <ajstewart@anl.gov>
To: 26240@debbugs.gnu.org
Subject: bug#26240: Guile doesn't search for libraries installed in /usr/lib64
Date: Fri, 24 Mar 2017 16:59:27 +0000 [thread overview]
Message-ID: <9F5501637440B04B9DE4C86279C60B6E4A5A9CA0@PAYTON.anl.gov> (raw)
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
Hi,
I'm trying to build Guile 2.2.0 on CentOS 7.3 with GCC 4.8.5. During configure, I see the following error message:
checking for libltdl... no
configure: error: GNU libltdl (Libtool) not found, see README.
I do have libtool installed on my system:
$ which libtool
/usr/bin/libtool
$ libtool --version
libtool (GNU libtool) 2.4.2
Written by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I'm passing the following option to configure:
$ ./configure --with-libltdl-prefix=/usr
but it still doesn't pick up libltdl. Based on the following help message:
$ ./configure --help
...
--with-libltdl-prefix[=DIR] search for libltdl in DIR/include and DIR/lib
I believe the problem is that CentOS installs libltdl to /usr/lib64 instead of /usr/lib:
$ ls -l /usr/lib64/libltdl.so.7*
lrwxrwxrwx 1 root root 16 Feb 27 11:19 /usr/lib64/libltdl.so.7 -> libltdl.so.7.3.0
-rwxr-xr-x 1 root root 41248 Feb 16 2016 /usr/lib64/libltdl.so.7.3.0
Do you have any suggestions as to how I can get Guile to pick up libraries installed in /usr/lib64?
Adam J. Stewart
Assistant Systems Administrator
Laboratory Computing Resource Center
Computing, Environment and Life Sciences
Argonne National Laboratory
[-- Attachment #2: Type: text/html, Size: 2906 bytes --]
next reply other threads:[~2017-03-24 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 16:59 Stewart, Adam James [this message]
2017-04-19 13:52 ` bug#26240: Guile doesn't search for libraries installed in /usr/lib64 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=9F5501637440B04B9DE4C86279C60B6E4A5A9CA0@PAYTON.anl.gov \
--to=ajstewart@anl.gov \
--cc=26240@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).