* guile 2.0.7 installation problems: configure issues libltdl error @ 2012-12-06 16:41 msematman 2012-12-06 18:23 ` Ludovic Courtès 2012-12-06 19:24 ` Mark H Weaver 0 siblings, 2 replies; 6+ messages in thread From: msematman @ 2012-12-06 16:41 UTC (permalink / raw) To: guile-user Dear all, I am a non-root user on a 64bit machine. I have been trying to install guile 2.0.7 from the tarball. After ordinary ./configure --prefix=$HOME/local or even just ./configure did not work, I have tried with: CC=gcc LDFLAGS="-L/usr/lib64/" ./configure --prefix=$HOME/local First few lines of the configure output: ******************************************* checking for a BSD-compatible install... The current directory must be set to the ITT directory. Change the default to the ITT directory and re-run this script. /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes ... ... ... Last line of configure output: ******************************** ... ... ... checking for libltdl... no and an error is issued complaining about the absence of libltdl. However, libltdl exists on the system: **************************** ls -l /usr/lib64/*ltdl* lrwxrwxrwx 1 root root 16 Nov 21 2011 /usr/lib64/libltdl.so.3 -> libltdl.so.3.1.4 -rwxr-xr-x 1 root root 29952 Dec 16 2009 /usr/lib64/libltdl.so.3.1.4 Why does the configure step break down? Is the library too old? A remark. The following snippet, "checking for a BSD-compatible install... The current directory must be set to the ITT directory. Change the default to the ITT directory and re-run this script." occurs because the IDL is in my PATH as well, and it contains an executable named install. I don't know if this confused the configure script. It seems not. Kind regards -- msematman@myopera.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: guile 2.0.7 installation problems: configure issues libltdl error 2012-12-06 16:41 guile 2.0.7 installation problems: configure issues libltdl error msematman @ 2012-12-06 18:23 ` Ludovic Courtès 2012-12-06 19:24 ` Mark H Weaver 1 sibling, 0 replies; 6+ messages in thread From: Ludovic Courtès @ 2012-12-06 18:23 UTC (permalink / raw) To: msematman; +Cc: guile-user Hi, msematman@myopera.com skribis: > checking for libltdl... no > > and an error is issued complaining about the absence of libltdl. > > However, libltdl exists on the system: > **************************** > ls -l /usr/lib64/*ltdl* > > lrwxrwxrwx 1 root root 16 Nov 21 2011 /usr/lib64/libltdl.so.3 -> > libltdl.so.3.1.4 > -rwxr-xr-x 1 root root 29952 Dec 16 2009 /usr/lib64/libltdl.so.3.1.4 > > > Why does the configure step break down? Is the library too old? Can you please look for the line ‘checking for libltdl’ in the file ‘config.log’, and post the details that follow? Thanks, Ludo’. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: guile 2.0.7 installation problems: configure issues libltdl error 2012-12-06 16:41 guile 2.0.7 installation problems: configure issues libltdl error msematman 2012-12-06 18:23 ` Ludovic Courtès @ 2012-12-06 19:24 ` Mark H Weaver 2012-12-07 12:17 ` msematman 1 sibling, 1 reply; 6+ messages in thread From: Mark H Weaver @ 2012-12-06 19:24 UTC (permalink / raw) To: msematman; +Cc: guile-user msematman@myopera.com writes: > Last line of configure output: > ******************************** > ... > ... > ... > checking for libltdl... no > > and an error is issued complaining about the absence of libltdl. > > However, libltdl exists on the system: > **************************** > ls -l /usr/lib64/*ltdl* > > lrwxrwxrwx 1 root root 16 Nov 21 2011 /usr/lib64/libltdl.so.3 -> > libltdl.so.3.1.4 > -rwxr-xr-x 1 root root 29952 Dec 16 2009 /usr/lib64/libltdl.so.3.1.4 Most likely, this is because you don't have /usr/include/ltdl.h, which is needed to compile programs against libltdl. Modern distributions typically separate libraries into at least two packages: the main package, and a "development package" which includes header files, etc, needed during compilation. For example, on Debian-derived systems, the main package is called "libltdl7", and the development package is called "libltdl-dev". To compile Guile, you will need the development packages for all of the libraries needed for Guile. If you cannot persuade the administrator of your system to install the needed packages, then there are a number of ways to proceed. The most straightforward is to compile+install the needed libraries from source code into your home directory, and then build Guile against those locally-installed libraries. There are a few gotchas, but it is doable. Regards, Mark ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: guile 2.0.7 installation problems: configure issues libltdl error 2012-12-06 19:24 ` Mark H Weaver @ 2012-12-07 12:17 ` msematman 2012-12-07 15:54 ` dsmich 0 siblings, 1 reply; 6+ messages in thread From: msematman @ 2012-12-07 12:17 UTC (permalink / raw) To: Mark H Weaver; +Cc: guile-user On Thu, Dec 6, 2012, at 08:24 PM, Mark H Weaver wrote: > msematman@myopera.com writes: > > Last line of configure output: > > ******************************** > > ... > > ... > > ... > > checking for libltdl... no > > > > and an error is issued complaining about the absence of libltdl. > > > > However, libltdl exists on the system: > > **************************** > > ls -l /usr/lib64/*ltdl* > > > > lrwxrwxrwx 1 root root 16 Nov 21 2011 /usr/lib64/libltdl.so.3 -> > > libltdl.so.3.1.4 > > -rwxr-xr-x 1 root root 29952 Dec 16 2009 /usr/lib64/libltdl.so.3.1.4 > > Most likely, this is because you don't have /usr/include/ltdl.h, which > is needed to compile programs against libltdl. > > Modern distributions typically separate libraries into at least two > packages: the main package, and a "development package" which includes > header files, etc, needed during compilation. For example, on > Debian-derived systems, the main package is called "libltdl7", and the > development package is called "libltdl-dev". > > To compile Guile, you will need the development packages for all of the > libraries needed for Guile. > > If you cannot persuade the administrator of your system to install the > needed packages, then there are a number of ways to proceed. The most > straightforward is to compile+install the needed libraries from source > code into your home directory, and then build Guile against those > locally-installed libraries. There are a few gotchas, but it is doable. > > Regards, > Mark Thanks Ludo', Mark for the quick responses. /usr/include on the machine does not contain ltdl.h, but /usr/share/libtool/libltdl/ does. I tried the following combo: CC=gcc CFLAGS="-I/usr/share/libtool/libltdl/" LDFLAGS="-L/usr/lib64/" ./configure --prefix=$HOME/local Still the same result, the exact same error. A tiny excerpt from the config.log (if somebody wants more of it, let me know): ... ... configure:40108: checking for libltdl configure:40130: gcc -o conftest -I/usr/share/libtool/libltdl/ -L/usr/lib64/ conftest.c -lltdl >&5 /usr/bin/ld: cannot find -lltdl collect2: ld returned 1 exit status configure:40130: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "GNU Guile" | #define PACKAGE_TARNAME "guile" | #define PACKAGE_VERSION "2.0.7" | #define PACKAGE_STRING "GNU Guile 2.0.7" | #define PACKAGE_BUGREPORT "bug-guile@gnu.org" | #define PACKAGE_URL "http://www.gnu.org/software/guile/" ... ... ... -- msematman@myopera.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: guile 2.0.7 installation problems: configure issues libltdl error 2012-12-07 12:17 ` msematman @ 2012-12-07 15:54 ` dsmich 2012-12-07 16:30 ` msematman 0 siblings, 1 reply; 6+ messages in thread From: dsmich @ 2012-12-07 15:54 UTC (permalink / raw) To: msematman, Mark H Weaver; +Cc: guile-user ---- msematman@myopera.com wrote: > On Thu, Dec 6, 2012, at 08:24 PM, Mark H Weaver wrote: > > msematman@myopera.com writes: > > > Last line of configure output: > > > ******************************** > > > ... > > > ... > > > ... > > > checking for libltdl... no > > > > > > and an error is issued complaining about the absence of libltdl. > > > > > > However, libltdl exists on the system: > > > **************************** > > > ls -l /usr/lib64/*ltdl* > > > > > > lrwxrwxrwx 1 root root 16 Nov 21 2011 /usr/lib64/libltdl.so.3 -> > > > libltdl.so.3.1.4 > > > -rwxr-xr-x 1 root root 29952 Dec 16 2009 /usr/lib64/libltdl.so.3.1.4 > > > > Most likely, this is because you don't have /usr/include/ltdl.h, which > > is needed to compile programs against libltdl. > > > > Modern distributions typically separate libraries into at least two > > packages: the main package, and a "development package" which includes > > header files, etc, needed during compilation. For example, on > > Debian-derived systems, the main package is called "libltdl7", and the > > development package is called "libltdl-dev". > > > > To compile Guile, you will need the development packages for all of the > > libraries needed for Guile. > > > > If you cannot persuade the administrator of your system to install the > > needed packages, then there are a number of ways to proceed. The most > > straightforward is to compile+install the needed libraries from source > > code into your home directory, and then build Guile against those > > locally-installed libraries. There are a few gotchas, but it is doable. > > > > Regards, > > Mark > > > Thanks Ludo', Mark for the quick responses. > > /usr/include on the machine does not contain ltdl.h, but > /usr/share/libtool/libltdl/ does. > > I tried the following combo: > CC=gcc CFLAGS="-I/usr/share/libtool/libltdl/" LDFLAGS="-L/usr/lib64/" > ./configure --prefix=$HOME/local > > Still the same result, the exact same error. Does it work better if you leave of the /'s from -I and -L ? -Dale ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: guile 2.0.7 installation problems: configure issues libltdl error 2012-12-07 15:54 ` dsmich @ 2012-12-07 16:30 ` msematman 0 siblings, 0 replies; 6+ messages in thread From: msematman @ 2012-12-07 16:30 UTC (permalink / raw) To: dsmich, Mark H Weaver; +Cc: guile-user On Fri, Dec 7, 2012, at 04:54 PM, dsmich@roadrunner.com wrote: > > ---- msematman@myopera.com wrote: > > On Thu, Dec 6, 2012, at 08:24 PM, Mark H Weaver wrote: > > > msematman@myopera.com writes: > > > > Last line of configure output: > > > > ******************************** > > > > ... > > > > ... > > > > ... > > > > checking for libltdl... no > > > > > > > > and an error is issued complaining about the absence of libltdl. > > > > > > > > However, libltdl exists on the system: > > > > **************************** > > > > ls -l /usr/lib64/*ltdl* > > > > > > > > lrwxrwxrwx 1 root root 16 Nov 21 2011 /usr/lib64/libltdl.so.3 -> > > > > libltdl.so.3.1.4 > > > > -rwxr-xr-x 1 root root 29952 Dec 16 2009 /usr/lib64/libltdl.so.3.1.4 > > > > > > Most likely, this is because you don't have /usr/include/ltdl.h, which > > > is needed to compile programs against libltdl. > > > > > > Modern distributions typically separate libraries into at least two > > > packages: the main package, and a "development package" which includes > > > header files, etc, needed during compilation. For example, on > > > Debian-derived systems, the main package is called "libltdl7", and the > > > development package is called "libltdl-dev". > > > > > > To compile Guile, you will need the development packages for all of the > > > libraries needed for Guile. > > > > > > If you cannot persuade the administrator of your system to install the > > > needed packages, then there are a number of ways to proceed. The most > > > straightforward is to compile+install the needed libraries from source > > > code into your home directory, and then build Guile against those > > > locally-installed libraries. There are a few gotchas, but it is doable. > > > > > > Regards, > > > Mark > > > > > > Thanks Ludo', Mark for the quick responses. > > > > /usr/include on the machine does not contain ltdl.h, but > > /usr/share/libtool/libltdl/ does. > > > > I tried the following combo: > > CC=gcc CFLAGS="-I/usr/share/libtool/libltdl/" LDFLAGS="-L/usr/lib64/" > > ./configure --prefix=$HOME/local > > > > Still the same result, the exact same error. > > Does it work better if you leave of the /'s from -I and -L ? > > -Dale > All right, I got the configure to finish without complaining. The libltdl problem went away when I softlinked the libltdl.so.3.1.4 as $HOME/local/lib64/libltdl.so . I didn't know that version number after 'so' matters for using the '-l' flag. No such luck with gc and unistring libraries which i had to download and install separately. Thanks for all the pointers! Todor -- msematman@myopera.com ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-12-07 16:30 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-12-06 16:41 guile 2.0.7 installation problems: configure issues libltdl error msematman 2012-12-06 18:23 ` Ludovic Courtès 2012-12-06 19:24 ` Mark H Weaver 2012-12-07 12:17 ` msematman 2012-12-07 15:54 ` dsmich 2012-12-07 16:30 ` msematman
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).