From: Grant Likely <grant.likely@secretlab.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Feedback ?
Date: Mon, 20 Oct 2008 08:52:29 -0600 [thread overview]
Message-ID: <20081020145229.GA10604@secretlab.ca> (raw)
In-Reply-To: <20081020154814.060a5b95@surf>
On Mon, Oct 20, 2008 at 03:48:14PM +0200, Thomas Petazzoni wrote:
> Le Wed, 15 Oct 2008 16:47:37 +0200,
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
>
> > Make sure libraries are visible when building packages
> >
> > This patch adds an LDFLAGS variable before calling the configure
> > script of any package, in order to fix two problems :
> >
> > * Some configure scripts were not able to compile the test programs
> > used to test whether zlib was properly installed. The configure
> > scripts are properly using -lz, but the
> > -L/path/to/staging_dir/usr/lib option was not present, leading to
> > build failure.
> >
> > * While linking applications, for example the applications included
> > in the fontconfig package, I had build failures like :
> >
> > /usr/local/uclibc-0.9.28-2/arm/lib/gcc/arm-linux-uclibc/3.4.5/../../../../arm-linux-uclibc/bin/ld.real:
> > warning: libfreetype.so.6, needed by ../src/.libs/libfontconfig.so,
> > not found (try using -rpath or -rpath-link)
> >
> > this is due to the fact that ld is not able to find the other
> > already installed shared libraries.
>
> May I have some feedback on this patch ? Without this, Buildroot is
> just unusable here.
FWIW, this patch looks good to me, but I'm far from the most
knowledgable person to comment.
g.
prev parent reply other threads:[~2008-10-20 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 14:47 [Buildroot] [PATCH] FIx libpng, directfb, dbus, fontconfig, etc. builds Thomas Petazzoni
2008-10-20 13:48 ` [Buildroot] Feedback ? Thomas Petazzoni
2008-10-20 13:55 ` Daniel Laird
2008-10-20 14:52 ` Grant Likely [this message]
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=20081020145229.GA10604@secretlab.ca \
--to=grant.likely@secretlab.ca \
--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