All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: openembedded-devel@openembedded.org
Subject: Re: Why is package external-toolchain-1.0 failing?
Date: Thu, 13 Dec 2007 04:18:24 +0000 (UTC)	[thread overview]
Message-ID: <fjqbqg$3td$1@ger.gmane.org> (raw)
In-Reply-To: 19c1b8a90712121930i73dcf071wff373d0d9e4fc6c6@mail.gmail.com

On 2007-12-13, Khem Raj <raj.khem@gmail.com> wrote:

> Can you attach your local conf file that you might have created.

I believe that the key is this line:

>>> NOTE: multiple providers are available for virtual/arm-angstrom-linux-binutils (external-toolchain, binutils-cross);
>>> NOTE: consider defining PREFERRED_PROVIDER_virtual/arm-angstrom-linux-binutils

I added a line in local.conf to set the preferred provider for
virtual/arm-angstrom-linux-binutils to binutils-cross, and now
things appear to be building (it's been building for an hour or
so now, which is way farther than it got before).

For some reason the example local.conf.sample incudes the
following

  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"

but doesn't doesn't select binutils-cross. I would suggest
adding this line to local.conf.sample:

  PREFERRED_PROVIDERS += "virtual/${TARGET_PREFIX}binutils:binutils-cross"

Or at least mentioning it on the "Getting Started" page,
because if you follow the steps on that page exactly, it won't
work unless you add the above line to local.conf.

-- 
Grant





  reply	other threads:[~2007-12-13  4:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  1:30 Why is package external-toolchain-1.0 failing? Grant Edwards
2007-12-13  3:10 ` Jacob Thebault-Spieker
2007-12-13  3:30   ` Khem Raj
2007-12-13  4:18     ` Grant Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-13  4:18 Mike Westerhof

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='fjqbqg$3td$1@ger.gmane.org' \
    --to=grante@visi.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.