unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: msematman@myopera.com, Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: guile 2.0.7 installation problems: configure issues libltdl error
Date: Fri, 7 Dec 2012 10:54:25 -0500	[thread overview]
Message-ID: <20121207155425.U2SP9.142330.root@cdptpa-web09-z01> (raw)
In-Reply-To: <1354882667.27227.140661163072321.02BFD8AA@webmail.messagingengine.com>


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




  reply	other threads:[~2012-12-07 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2012-12-07 16:30       ` msematman

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=20121207155425.U2SP9.142330.root@cdptpa-web09-z01 \
    --to=dsmich@roadrunner.com \
    --cc=guile-user@gnu.org \
    --cc=mhw@netris.org \
    --cc=msematman@myopera.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).