From: "Kevin F. Quinn (Gentoo)" <kevquinn@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Building Crosscompiler for Embedded System
Date: Mon, 6 Mar 2006 20:14:35 +0100 [thread overview]
Message-ID: <20060306201435.75ea4833@c1358217.kevquinn.com> (raw)
In-Reply-To: <440C024E.8000608@sit.fraunhofer.de>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Mon, 06 Mar 2006 10:35:10 +0100
Lutz Schönemann <lutz.schoenemann@sit.fraunhofer.de> wrote:
> Hi,
> I've problems building an working Cross-Compiler to use it for an
> i386 embedded system. Until now I've tried the following two things:
>
> - Using crossdev:
> The crossdev script worked fine and installed the whole toolchain
> (stage4: binutils, gcc, linux-headers, etc.). The trouble is that
> when I want to merge a packege with this compiler (e.g.:
> CFLAGS="-arch=i386" ROOT=/tmp/cross/ CHOST=i386-unknown-linux-gnu
> emerge sys-boot/syslinux) it ends up with the message that the
> compiler is unable to build executables.
Just in case that wasn't a typo in transcription - you need
CFLAGS="-march=i386" (with an 'm'). You should look at the config.log
etc to find out exactly why the compiler couldn't build executables.
BTW again just in case - if your host is an x86 system, you don't need a
cross-compiler as your host compiler can build for all x86 variants -
it's enough to get the CFLAGS right; e.g.
CFLAGS="-march=i386" ROOT=/tmp/cross emerge <pkg>
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-06 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 9:35 [gentoo-embedded] Building Crosscompiler for Embedded System Lutz Schönemann
2006-03-06 14:16 ` Mike Frysinger
2006-03-06 14:43 ` Lutz Schönemann
2006-03-06 14:50 ` Mike Frysinger
2006-03-06 19:14 ` Kevin F. Quinn (Gentoo) [this message]
2006-03-07 12:42 ` Lutz Schönemann
2006-03-07 16:27 ` Stanisław Raczyński
2006-03-08 5:31 ` Mike Frysinger
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=20060306201435.75ea4833@c1358217.kevquinn.com \
--to=kevquinn@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
/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