From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: gcc-cross-initial.inc DEPENDS on libc-initial, but why conditionally on TARGET_ARCH?
Date: Mon, 10 Mar 2008 17:48:22 +0100 [thread overview]
Message-ID: <fr3oom$clq$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0803091149g321e7086qec5b54499c7ecbc@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Leon Woestenberg schreef:
| Hello,
|
| OE toolchain question: any reason why the list below includes arm*,
| mips* but nothing else?
|
| gcc-cross-initial.inc:
|
| DEPENDS = "virtual/${TARGET_PREFIX}binutils"
| DEPENDS +=
"${@['virtual/${TARGET_PREFIX}libc-initial',''][bb.data.getVar('TARGET_ARCH',
| d, 1) in ['arm', 'armeb', 'mips', 'mipsel']]}"
| PROVIDES = "virtual/${TARGET_PREFIX}gcc-initial"
| PACKAGES = ""
|
| (I'm tracking down a parallel make issue, this seems to cause/trigger
| it as I build for powerpc).
I think that's because we only supported nptl for arm and mips when the
earth was still young and glibc even nastier than today. I asked this
before and never got a conclusive answer :(
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH1WZWMkyGM64RGpERAiclAKC86eWW8nzBnK7qXIsSnpRbdifdZQCeL2fV
LJmhpyxT15Hm854ErQYmJtg=
=9ahN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-10 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 18:49 gcc-cross-initial.inc DEPENDS on libc-initial, but why conditionally on TARGET_ARCH? Leon Woestenberg
2008-03-10 16:48 ` Koen Kooi [this message]
2008-03-10 17:56 ` Leon Woestenberg
2008-03-10 22:27 ` Richard Purdie
2008-03-10 23:01 ` Leon Woestenberg
2008-03-11 1:46 ` 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='fr3oom$clq$1@ger.gmane.org' \
--to=koen@dominion.kabel.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 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.