From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] The issue is link_all_deplibs libtool config variable
Date: Thu, 9 Oct 2008 11:43:43 +0200 [thread overview]
Message-ID: <20081009114343.2eabb7e6@surf> (raw)
In-Reply-To: <20081007165610.4de3f377@surf>
Le Tue, 7 Oct 2008 16:56:10 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> The ../src/.libs/libfontconfig.so properly references the .la files of
> libexpat and libfreetype. If I had these path to the .la files to the
> big libtool command line, then it links properly.
>
> Any clue about this problem ?
It seems that the problem is caused by libtool configuration variable
"link_all_deplibs" being set to "no".
This problem has been reported here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=297726. It seems that
setting link_all_deplibs to yes works for native compilation, but not
from cross-compilation. The patch seems be to be Debian-specific, and
I'm an Ubuntu user, so I inherited this patch.
As a quick and gory hack, I modified the configure to replace all
instances of link_all_deplibs=no by link_all_deplibs=yes. And the
compilation now works properly.
What's the proper way of fixing this ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-10-09 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 14:56 [Buildroot] Issue with libtool while building/linking fontconfig Thomas Petazzoni
2008-10-08 6:24 ` Thomas Petazzoni
2008-10-09 9:43 ` Thomas Petazzoni [this message]
2008-10-15 8:50 ` [Buildroot] The issue is link_all_deplibs libtool config variable Thomas Petazzoni
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=20081009114343.2eabb7e6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.