Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Heads up: staging changes are going to land
Date: Mon, 06 Oct 2008 21:38:27 +0200	[thread overview]
Message-ID: <gcdpfj$hr0$1@ger.gmane.org> (raw)
In-Reply-To: <gcdokp$evo$1@ger.gmane.org>

On 06-10-2008 21:24, Koen Kooi wrote:
> On 06-10-2008 21:10, Leon Woestenberg wrote:
>> Hello Koen,
>>
>> this change in that patch:
>>
>> +CROSS_DIR = "${TMPDIR}/cross/${BASE_PACKAGE_ARCH}"
>>
>> makes my OE PATH look like this:
>>
>> <...>/build/tmp/cross/ppce300c3/bin
>>
>> but my cross toolchain did not end up there, instead it ended up in
>> the usual place:<...>/build/tmp/cross/bin/
>
> My cross looks like this:
>
> koen@dominion:/OE/angstrom-dev/cross$ ls
> arm-oabi/ armv4t/ armv5te/ armv6/ armv7a/ avr32/ ppc405/ ppc603e/
>
>  > so I am getting:
>>
>> NOTE: make -j5 -e MAKEFLAGS= include/linux/version.h CC=ccache
>> powerpc-angstrom-linux-gcc LD=powerpc-angstrom-linux-ld
>> powerpc-angstrom-linux-gcc: No such file or directory
>>
>> So obviously for me the CROSS_DIR is not respected somehow for the
>> toolchain.
>>
>> Any ideas where it could leak away?
>>
>> I did a scratch build against HEAD using the latest stable bitbake
>> tree checkout, for MACHINE=mpc8313erdb.
>>
>> Some other details might still exist at
>> http://tinderbox.openembedded.net/builders/likewise/
>
> I'm starting a build with that machine to see if I can reproduce it.

I now have:

koen@dominion:/OE/angstrom-dev/cross$ ls
arm-oabi/  armv4t/  armv5te/  armv6/  armv7a/  avr32/  ppc405/  ppc603e/ 
  ppce300c3/
koen@dominion:/OE/angstrom-dev/cross$ find ppce300c3/ | grep -- -gcc
ppce300c3/bin/powerpc-angstrom-linux-gcc
ppce300c3/bin/powerpc-angstrom-linux-gccbug
ppce300c3/bin/powerpc-angstrom-linux-gcc-4.2.4

I suspect packaged-staging is using the old staging packages (as can be 
seen from the do_setscene in the gcc tinderbox log). Could you try it 
without keeping pstage?

regards,

Koen




  reply	other threads:[~2008-10-06 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 18:53 Heads up: staging changes are going to land Koen Kooi
2008-10-02 22:25 ` Richard Purdie
2008-10-03  7:12   ` Koen Kooi
2008-10-03  8:19     ` Phil Blundell
2008-10-03  8:41     ` Stanislav Brabec
2008-10-03  7:23   ` Koen Kooi
2008-10-03  8:24     ` Richard Purdie
2008-10-06 19:10 ` Leon Woestenberg
2008-10-06 19:24   ` Koen Kooi
2008-10-06 19:38     ` Koen Kooi [this message]
2008-10-06 23:01       ` Leon Woestenberg
2008-10-07  8:29         ` Leon Woestenberg
2008-10-07  9:26           ` Koen Kooi

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='gcdpfj$hr0$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox