Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] adding libgphoto2
Date: Sat, 4 Jun 2011 10:38:44 +0200	[thread overview]
Message-ID: <20110604103844.7cb3a129@surf> (raw)
In-Reply-To: <4DE33733.6090305@pender.dnsalias.net>

Hello,

On Sun, 29 May 2011 23:20:35 -0700
Niall Parker <stuff@pender.dnsalias.net> wrote:

> I've been using buildroot 2011.02 and was trying to libgphoto2 and
> was following the howto in the docs (also copying the libusb
> Config.in and .mk with tweaks). Unfortunately it wasn't a trivial
> task and it is complaining it needs libltdl ...
> 
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > checking ltdl.h usability... no
> > checking ltdl.h presence... no
> > checking for ltdl.h... no
> > checking that we can compile and link with libltdl... no
> > configure: error: cannot compile and link against libltdl
> > libgphoto2 requires libltdl (the libtool dl* library),
> > but cannot compile and link against it.
> > Aborting.
> 
> I have enabled libtool in the package selection but evidently the 
> autoconf isn't finding it. Any suggestions on where to start ?

Can you share the current status of your patch, so that we can try to
help you starting from where you are ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-06-04  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  6:20 [Buildroot] adding libgphoto2 Niall Parker
2011-06-04  8:38 ` Thomas Petazzoni [this message]
2011-07-12 23:16   ` Niall Parker

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110604103844.7cb3a129@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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