Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: failure on gcc-cross-initial-4.2.4-r5 for i686
Date: Tue, 10 Mar 2009 20:41:02 -0700	[thread overview]
Message-ID: <200903102041.06686.raj.khem@gmail.com> (raw)
In-Reply-To: <20090311030509.GA10085@denix.org>

[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]

On Tuesday 10 March 2009 20:05:09 Denys Dmytriyenko wrote:
> On Tue, Mar 10, 2009 at 10:35:19AM -0700, Khem Raj wrote:
> > On Tue, Mar 10, 2009 at 8:40 AM, Travis Stratman <tstratman@emacinc.com> 
wrote:
> > > Thanks Khem.
> > >
> > > On Mon, 2009-03-09 at 15:35 -0700, Khem Raj wrote:
> > >> On Mon, Mar 9, 2009 at 3:18 PM, Travis Stratman
> > >> <tstratman@emacinc.com> wrote:
> > >>
> > >> snip
> > >>
> > >> > PREFERRED_PROVIDERS += "
> > >> > virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial"
> > >> > PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross"
> > >> > PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross"
> > >>
> > >> Can you try by removing above three
> > >>
> > >> Rest of the changes seems like should not have effect.
> > >
> > > This doesn't seem to change anything. I made the changes, cleaned all
> > > glibc and gcc packages, then tried to build and I still get the same
> > > issue.
> > >
> > > Any other ideas?
> >
> > Hmm looking closely it seems that your cross compiler is from
> > i686-linux -> i686-linux which is native configuration and intl
> > configury  is then trying to use
> > your freshly built CC instead of the BUILD_CC. In short its not really
> > thinking if it is cross compiling. I have a x86_64 box thats why it
> > worked for me because I am cross'ing from x86_64-linux to i686-linux
> >
> > I will give it a shot on x86 box too. Meanwhile can you also define
> > TARGET_VENDOR = "something" for your distr and rebuild
>
> I'll save you some trouble - been building i686-generic on I32 x86 for
> months w/o a problem. Angstrom distro with a small overlay - configuration
> is pretty basic.
>
[snip]
> i686-linux holds my native packages
> i686-angstrom-linux holds my target/cross packages, including gcc-cross

Yeah this makes your target triplet different then your host triplet and hence 
it compiles a correct cross gcc for you.

> i686-generic-angstrom-linux holds machine-specific target packages

-- 
Khem Raj

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

  reply	other threads:[~2009-03-11  3:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07 22:07 failure on gcc-cross-initial-4.2.4-r5 for i686 Travis Stratman
2009-03-08  1:35 ` Khem Raj
2009-03-09 22:18   ` Travis Stratman
2009-03-09 22:35     ` Khem Raj
2009-03-10 15:40       ` Travis Stratman
2009-03-10 17:35         ` Khem Raj
2009-03-11  3:05           ` Denys Dmytriyenko
2009-03-11  3:41             ` Khem Raj [this message]
2009-03-11 21:28             ` Leon Woestenberg
2009-03-12  2:22               ` Denys Dmytriyenko
2009-03-13 21:22             ` Stanislav Brabec
2009-03-11 15:36           ` Travis Stratman
2009-03-11 22:44           ` Travis Stratman

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=200903102041.06686.raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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