* Why is package external-toolchain-1.0 failing?
@ 2007-12-13 1:30 Grant Edwards
2007-12-13 3:10 ` Jacob Thebault-Spieker
0 siblings, 1 reply; 5+ messages in thread
From: Grant Edwards @ 2007-12-13 1:30 UTC (permalink / raw)
To: openembedded-devel
I've followed the step-by-step instructions on the "getting
started with OE" web page for a Zaurus SL5500, but when I try
to do the example build command "bitbake nano" it fails.
Google didn't really find anything that seemed helpful. I
searched the mailing list and found a posting a coule weeks ago
from somebody who had the exact same issue, but that posting
got no useful responses (possibly because it hijacked a
thread).
What is an "external toolchain", do I need one to build for an
SL5500 target? If I do need one, why doesn't bitbake know how
to build one?
Here's the output from the "bitbake nano" command:
________________________________________________________________________
Parsing .bb files, please wait...done.
NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
NOTE: build 200712121925: started
OE Build Configuration:
BB_VERSION = "1.8.8"
OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
TARGET_ARCH = "arm"
TARGET_OS = "linux"
MACHINE = "collie"
DISTRO = "angstrom"
DISTRO_VERSION = "2007.9-test-20071213"
TARGET_FPU = "soft"
NOTE: Resolving missing task queue dependencies
NOTE: multiple providers are available for linux-libc-headers (linux-libc-headers, external-toolchain);
NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
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
NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-libc-for-gcc)
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 88 of 281 (ID: 126, /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging)
NOTE: package external-toolchain-1.0: started
NOTE: package external-toolchain-1.0-r1: task do_populate_staging: started
ERROR: function do_stage failed
ERROR: log data follows (/home/grante/quarq/oe/tmp/work/i686-arm-oabi-sdk-angstrom-linux/external-toolchain-1.0-r1/temp/log.do_stage.8896)
| The external toolchain could not be found in /usr/local/angstrom/arm!
NOTE: Task failed: /home/grante/quarq/oe/tmp/work/i686-arm-oabi-sdk-angstrom-linux/external-toolchain-1.0-r1/temp/log.do_stage.8896
NOTE: package external-toolchain-1.0-r1: task do_populate_staging: failed
ERROR: TaskFailed event exception, aborting
NOTE: package external-toolchain-1.0: failed
ERROR: Build of /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb do_populate_staging failed
NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
NOTE: build 200712121925: started
OE Build Configuration:
BB_VERSION = "1.8.8"
OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
TARGET_ARCH = "arm"
TARGET_OS = "linux"
MACHINE = "collie"
DISTRO = "angstrom"
DISTRO_VERSION = "2007.9-test-20071213"
TARGET_FPU = "soft"
NOTE: Resolving missing task queue dependencies
NOTE: multiple providers are available for linux-libc-headers (linux-libc-headers, external-toolchain);
NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
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
NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-libc-for-gcc)
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 88 of 281 (ID: 126, /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging)
ERROR: Task 126 (/home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging) failed
NOTE: Tasks Summary: Attempted 87 tasks of which 87 didn't need to be rerun and 1 failed.
ERROR: '/home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb' failed
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Why is package external-toolchain-1.0 failing?
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
0 siblings, 1 reply; 5+ messages in thread
From: Jacob Thebault-Spieker @ 2007-12-13 3:10 UTC (permalink / raw)
To: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I was having that trouble, and I'm not exactly sure what happened, but
it magically fixed itself. I just kept updating every day, and I believe
I re-pulled the tree at one point. Again, I don't know why my build
wasn't finishing, it kept throwing errors that weren't true. Regardless,
it fixed itself, sorry I can't be more help.
- --
Jacob Thebault-Spieker
Cell: (207) 717-5114
Grant Edwards wrote:
> I've followed the step-by-step instructions on the "getting
> started with OE" web page for a Zaurus SL5500, but when I try
> to do the example build command "bitbake nano" it fails.
> Google didn't really find anything that seemed helpful. I
> searched the mailing list and found a posting a coule weeks ago
> from somebody who had the exact same issue, but that posting
> got no useful responses (possibly because it hijacked a
> thread).
>
> What is an "external toolchain", do I need one to build for an
> SL5500 target? If I do need one, why doesn't bitbake know how
> to build one?
>
> Here's the output from the "bitbake nano" command:
>
> ________________________________________________________________________
> Parsing .bb files, please wait...done.
> NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
> NOTE: build 200712121925: started
>
> OE Build Configuration:
> BB_VERSION = "1.8.8"
> OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
> TARGET_ARCH = "arm"
> TARGET_OS = "linux"
> MACHINE = "collie"
> DISTRO = "angstrom"
> DISTRO_VERSION = "2007.9-test-20071213"
> TARGET_FPU = "soft"
>
> NOTE: Resolving missing task queue dependencies
> NOTE: multiple providers are available for linux-libc-headers (linux-libc-headers, external-toolchain);
> NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
> 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
> NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-libc-for-gcc)
> NOTE: Preparing runqueue
> NOTE: Executing runqueue
> NOTE: Running task 88 of 281 (ID: 126, /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging)
> NOTE: package external-toolchain-1.0: started
> NOTE: package external-toolchain-1.0-r1: task do_populate_staging: started
> ERROR: function do_stage failed
> ERROR: log data follows (/home/grante/quarq/oe/tmp/work/i686-arm-oabi-sdk-angstrom-linux/external-toolchain-1.0-r1/temp/log.do_stage.8896)
> | The external toolchain could not be found in /usr/local/angstrom/arm!
> NOTE: Task failed: /home/grante/quarq/oe/tmp/work/i686-arm-oabi-sdk-angstrom-linux/external-toolchain-1.0-r1/temp/log.do_stage.8896
> NOTE: package external-toolchain-1.0-r1: task do_populate_staging: failed
> ERROR: TaskFailed event exception, aborting
> NOTE: package external-toolchain-1.0: failed
> ERROR: Build of /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb do_populate_staging failed
>
> NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
> NOTE: build 200712121925: started
>
> OE Build Configuration:
> BB_VERSION = "1.8.8"
> OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
> TARGET_ARCH = "arm"
> TARGET_OS = "linux"
> MACHINE = "collie"
> DISTRO = "angstrom"
> DISTRO_VERSION = "2007.9-test-20071213"
> TARGET_FPU = "soft"
>
> NOTE: Resolving missing task queue dependencies
> NOTE: multiple providers are available for linux-libc-headers (linux-libc-headers, external-toolchain);
> NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
> 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
> NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-libc-for-gcc)
> NOTE: Preparing runqueue
> NOTE: Executing runqueue
> NOTE: Running task 88 of 281 (ID: 126, /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging)
> ERROR: Task 126 (/home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging) failed
> NOTE: Tasks Summary: Attempted 87 tasks of which 87 didn't need to be rerun and 1 failed.
> ERROR: '/home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb' failed
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHYKKttXjjJ1zu9YARAstxAJwPEf2DdK55zVcnSOtRNsYeD/piTgCgrBVc
oe3MdlRaq0wQExFvyUqDqNk=
=ybrf
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Why is package external-toolchain-1.0 failing?
2007-12-13 3:10 ` Jacob Thebault-Spieker
@ 2007-12-13 3:30 ` Khem Raj
2007-12-13 4:18 ` Grant Edwards
0 siblings, 1 reply; 5+ messages in thread
From: Khem Raj @ 2007-12-13 3:30 UTC (permalink / raw)
To: openembedded-devel
Can you attach your local conf file that you might have created.
Khem
On Dec 12, 2007 7:10 PM, Jacob Thebault-Spieker
<summatusmentis@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I was having that trouble, and I'm not exactly sure what happened, but
> it magically fixed itself. I just kept updating every day, and I believe
> I re-pulled the tree at one point. Again, I don't know why my build
> wasn't finishing, it kept throwing errors that weren't true. Regardless,
> it fixed itself, sorry I can't be more help.
>
> - --
> Jacob Thebault-Spieker
> Cell: (207) 717-5114
>
>
>
> Grant Edwards wrote:
> > I've followed the step-by-step instructions on the "getting
> > started with OE" web page for a Zaurus SL5500, but when I try
> > to do the example build command "bitbake nano" it fails.
> > Google didn't really find anything that seemed helpful. I
> > searched the mailing list and found a posting a coule weeks ago
> > from somebody who had the exact same issue, but that posting
> > got no useful responses (possibly because it hijacked a
> > thread).
> >
> > What is an "external toolchain", do I need one to build for an
> > SL5500 target? If I do need one, why doesn't bitbake know how
> > to build one?
> >
> > Here's the output from the "bitbake nano" command:
> >
> > ________________________________________________________________________
> > Parsing .bb files, please wait...done.
> > NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
> > NOTE: build 200712121925: started
> >
> > OE Build Configuration:
> > BB_VERSION = "1.8.8"
> > OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
> > TARGET_ARCH = "arm"
> > TARGET_OS = "linux"
> > MACHINE = "collie"
> > DISTRO = "angstrom"
> > DISTRO_VERSION = "2007.9-test-20071213"
> > TARGET_FPU = "soft"
> >
> > NOTE: Resolving missing task queue dependencies
> > NOTE: multiple providers are available for linux-libc-headers (linux-libc-headers, external-toolchain);
> > NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
> > 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
> > NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-libc-for-gcc)
> > NOTE: Preparing runqueue
> > NOTE: Executing runqueue
> > NOTE: Running task 88 of 281 (ID: 126, /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging)
> > NOTE: package external-toolchain-1.0: started
> > NOTE: package external-toolchain-1.0-r1: task do_populate_staging: started
> > ERROR: function do_stage failed
> > ERROR: log data follows (/home/grante/quarq/oe/tmp/work/i686-arm-oabi-sdk-angstrom-linux/external-toolchain-1.0-r1/temp/log.do_stage.8896)
> > | The external toolchain could not be found in /usr/local/angstrom/arm!
> > NOTE: Task failed: /home/grante/quarq/oe/tmp/work/i686-arm-oabi-sdk-angstrom-linux/external-toolchain-1.0-r1/temp/log.do_stage.8896
> > NOTE: package external-toolchain-1.0-r1: task do_populate_staging: failed
> > ERROR: TaskFailed event exception, aborting
> > NOTE: package external-toolchain-1.0: failed
> > ERROR: Build of /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb do_populate_staging failed
> >
> > NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
> > NOTE: build 200712121925: started
> >
> > OE Build Configuration:
> > BB_VERSION = "1.8.8"
> > OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
> > TARGET_ARCH = "arm"
> > TARGET_OS = "linux"
> > MACHINE = "collie"
> > DISTRO = "angstrom"
> > DISTRO_VERSION = "2007.9-test-20071213"
> > TARGET_FPU = "soft"
> >
> > NOTE: Resolving missing task queue dependencies
> > NOTE: multiple providers are available for linux-libc-headers (linux-libc-headers, external-toolchain);
> > NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
> > 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
> > NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-libc-for-gcc)
> > NOTE: Preparing runqueue
> > NOTE: Executing runqueue
> > NOTE: Running task 88 of 281 (ID: 126, /home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging)
> > ERROR: Task 126 (/home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb, do_populate_staging) failed
> > NOTE: Tasks Summary: Attempted 87 tasks of which 87 didn't need to be rerun and 1 failed.
> > ERROR: '/home/grante/quarq/oe/org.openembedded.dev/packages/meta/external-toolchain.bb' failed
> >
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHYKKttXjjJ1zu9YARAstxAJwPEf2DdK55zVcnSOtRNsYeD/piTgCgrBVc
> oe3MdlRaq0wQExFvyUqDqNk=
> =ybrf
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Why is package external-toolchain-1.0 failing?
2007-12-13 3:30 ` Khem Raj
@ 2007-12-13 4:18 ` Grant Edwards
0 siblings, 0 replies; 5+ messages in thread
From: Grant Edwards @ 2007-12-13 4:18 UTC (permalink / raw)
To: openembedded-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Why is package external-toolchain-1.0 failing?
@ 2007-12-13 4:18 Mike Westerhof
0 siblings, 0 replies; 5+ messages in thread
From: Mike Westerhof @ 2007-12-13 4:18 UTC (permalink / raw)
To: openembedded-devel
On Thu 13/12/07 1:30 AM , Grant Edwards grante@visi.com sent:
> I've followed the step-by-step instructions on the "getting
> started with OE" web page for a Zaurus SL5500, but when I try
> to do the example build command "bitbake nano" it fails.
> Google didn't really find anything that seemed helpful. I
> searched the mailing list and found a posting a coule weeks ago
> from somebody who had the exact same issue, but that posting
> got no useful responses (possibly because it hijacked a
> thread).
>
> What is an "external toolchain", do I need one to build for an
> SL5500 target? If I do need one, why doesn't bitbake know how
> to build one?
Oh, you don't want an external toolchain. Bitbake just has two possible choices,
and it chose the wrong one. And, yes, it should know how to build the external
toolchain, when that stuff actually works, there are a lot of computers (and
power plants) that won't have to work so hard to build stuff with OE.
> Here's the output from the "bitbake nano" command:
>
> ________________________________________________________________________
> Parsing .bb files, please wait...done.
> NOTE: Parsing finished. 4675 cached, 0 parsed, 218 skipped, 0 masked.
> NOTE: build 200712121925: started
>
> OE Build Configuration:
> BB_VERSION = "1.8.8"
> OE_REVISION = "47aec7f5811a7e41e48a85cc8ca83a9ef745e862"
> TARGET_ARCH = "arm"
> TARGET_OS = "linux"
> MACHINE = "collie"
> DISTRO = "angstrom"
> DISTRO_VERSION = "2007.9-test-20071213"
> TARGET_FPU = "soft"
>
> NOTE: Resolving missing task queue dependencies
> NOTE: multiple providers are available for linux-libc-headers
> (linux-libc-headers, external-toolchain);
> NOTE: consider defining PREFERRED_PROVIDER_linux-libc-headers
> 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
These preceding lines tell the tale. OE has multiple possible things that can
provide the dependencies, and it's chosen (arbitrarily) "external-toolchain". As
it suggests, add the following to your local.conf to dis-ambiguate (is that a word?):
PREFERRED_PROVIDER_linux-libc-headers = "linux-libc-headers"
PREFERRED_PROVIDER_virtual/arm-angstrom-linux-binutils = "binutils-cross"
Mike (mwester)
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-12-13 4:23 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- strict thread matches above, loose matches on Subject: below --
2007-12-13 4:18 Mike Westerhof
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.