From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] This linker was not configured to use sysroots
Date: Fri, 22 Jun 2007 13:24:00 +0200 [thread overview]
Message-ID: <20070622112400.GB31755@aon.at> (raw)
In-Reply-To: <009401c7b4ba$7613bbf0$2311a8c0@OneWorld.local>
On Fri, Jun 22, 2007 at 11:45:34AM +0100, Nuno da Costa Ferro wrote:
>Hello,
>
>I'm getting this error while compiling 'fontconfig':
>make[4]: Entering directory
>`/build/firmware/buildroot/build_arm/fontconfig-2.4.2/fc-case'
>/usr/bin/gcc -Os -pipe -I/build/firmware/buildroot/build_arm/staging_dir/usr/include
> --sysroot=/build/firmware/buildroot/build_arm/staging_dir/ -isysroot
>/build/firmware/buildroot/build_arm/staging_dir -L/build/firmware/buildroot/build_arm/staging_dir/lib
> -L/build/firmware/buildroot/build_arm/staging_dir/usr/lib -o fc-case
>fc-case.o
>
>/usr/bin/ld: this linker was not configured to use sysroots
IIRC this fc-case is ment to be run on the host (to create some stuff).
Last time i looked, fontconfig was utterly broken for cross-compiling.
I suggests you add -march=armv5 (or any arm* that matches your target)
to your BR2_TARGET_OPTIMIZATION, this will make it very, very clear
which packages are broken (are and also were even before the sysroot
support).
>
>What do I need to do in order to fix this?
fix fontconfig upstream so it can properly be cross-compiled, i.e. so
that it uses CC_FOR_BUILD CFLAGS_FOR_BUILD when creating binaries ment
to be run on the host, and CC/CFLAGS for stuff that is cross-compiled.
prev parent reply other threads:[~2007-06-22 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 10:45 [Buildroot] This linker was not configured to use sysroots Nuno da Costa Ferro
2007-06-22 11:24 ` Bernhard Fischer [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=20070622112400.GB31755@aon.at \
--to=rep.dot.nop@gmail.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