public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: wireless <wireless@tampabay.rr.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] CBUILD= HOSTCC=-gcc
Date: Tue, 04 Jan 2011 14:47:22 -0500	[thread overview]
Message-ID: <4D23794A.4090804@tampabay.rr.com> (raw)
In-Reply-To: <4D223B90.2010604@gmail.com>

On 01/03/11 16:11, Christoph Spielmann wrote:

> Well in terms of crossdev i686-gentoo-linux-gnu-gcc is not a valid
> target (just look at the output of crossdev --help). If you want to
> build x86-code on a machine using a x86-compiler why would you want to
> use a cross-compilation-environment anyway? The idea of using
> cross-compilation is to build stuff for another target than the target
> of the host-compiler... E.g. build arm-code on a x86-machine or compile
> stuff for ppc on a x86-64-machine.


OK I agree with this answer, mostly.

I have a situation where a x86 (P4) Machine is built on i686 for
everything. However, I'm also going to chroot the machine and build
binaries for all sorts of i486/586 and old oddball processors such as
the Geode.

So isn't that a valid exception to what you have opined about?


curious,
James




  parent reply	other threads:[~2011-01-04 20:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-02 17:40 [gentoo-embedded] CBUILD= HOSTCC=-gcc Kfir Lavi
2011-01-02 18:59 ` Peter Stuge
2011-01-02 19:31   ` Mike Frysinger
2011-01-03  9:21     ` Kfir Lavi
2011-01-03 12:17       ` Christoph Spielmann
2011-01-03 15:33         ` Kfir Lavi
2011-01-03 21:11           ` Christoph Spielmann
2011-01-04 15:57             ` Kfir Lavi
2011-01-04 19:47             ` wireless [this message]
2011-01-05  8:21               ` Christoph Spielmann
2011-02-05 15:31                 ` Enrico Weigelt
2011-02-05 15:24             ` Enrico Weigelt
2011-01-04 21:17         ` Mike Frysinger
2011-01-02 19:06 ` Christoph Spielmann

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=4D23794A.4090804@tampabay.rr.com \
    --to=wireless@tampabay.rr.com \
    --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