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] Problems with new revision.
Date: Mon, 10 Nov 2008 09:05:15 +0100	[thread overview]
Message-ID: <20081110090515.67210707@surf> (raw)
In-Reply-To: <4917D8AB.40404@genesysdesign.com.au>

Le Mon, 10 Nov 2008 17:46:03 +1100,
Jared Holzman <j.holzman@genesysdesign.com.au> a ?crit :

> Just updated to the latest revision using svn upd. I'm now having a 
> problem with compiling fontconfig, xlib_libX11 and xlib_libXt. The 
> problem seems to be that each package requires a host runnable 
> executable to be build and it is attempting to link it using target 
> flags. I've chased it down the following difference in the Makefiles:
> 
> -LDFLAGS =
> +LDFLAGS = -L/home/jared/src/buildroot/build_arm/staging_dir/lib 
> -L/home/jared/src/buildroot/build_arm/staging_dir/usr/lib 
> -Wl,--rpath-link
> -Wl,/home/jared/src/buildroot/build_arm/staging_dir/lib
> -Wl,--rpath-link
> -Wl,/home/jared/src/buildroot/build_arm/staging_dir/usr/lib
> --sysroot=/home/jared/src/buildroot/build_arm/staging_dir/
> 
> But I don't have enough experience with the build system to track
> down where this is coming from.

It's probably another bug of the fix we're trying to work on with
Daniel Laird. But the (incorrect) fix has been removed in r23954. Can
you update after this revision and see if you're still having the
problem ?

Moreover, can you send the .config with which you were having issues,
and the exact errors you were getting ?

Thanks,

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

      reply	other threads:[~2008-11-10  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  6:46 [Buildroot] Problems with new revision Jared Holzman
2008-11-10  8:05 ` Thomas Petazzoni [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=20081110090515.67210707@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