Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: failure on gcc-cross-initial-4.2.4-r5 for i686
Date: Wed, 11 Mar 2009 22:22:15 -0400	[thread overview]
Message-ID: <20090312022215.GB12341@denix.org> (raw)
In-Reply-To: <c384c5ea0903111428y4ffee26dud7662f1f614074ac@mail.gmail.com>

On Wed, Mar 11, 2009 at 10:28:09PM +0100, Leon Woestenberg wrote:
> Denys,
> 
> On Wed, Mar 11, 2009 at 4:05 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > i686-linux holds my native packages
> > i686-angstrom-linux holds my target/cross packages, including gcc-cross
> > i686-generic-angstrom-linux holds machine-specific target packages
> >
> Are that your overlay directory names?

Obviously, not. Those are my target and host triplets. Those are the 
directories used in work, stamps, staging and pkgdata among other things.

> Then they have nothing to do with the actual problem AFAIK.
> 
> It's probably the target triplet name that makes the difference, like
> Khem suggests.

Correct, as Khem suspected and Travis confirmed, not setting TARGET_VENDOR 
messes things up by clashing host and target triplets, which confuses the hell 
out of the cross-compilation :)
BTW, Angstrom sets it to "-angstrom" by default, as in my case.

-- 
Denys



  reply	other threads:[~2009-03-12  2:23 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
2009-03-11 21:28             ` Leon Woestenberg
2009-03-12  2:22               ` Denys Dmytriyenko [this message]
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=20090312022215.GB12341@denix.org \
    --to=denis@denix.org \
    --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