From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: 'LIBC' variable clashes with perl variable
Date: Sun, 11 Jul 2010 19:33:07 +0200 [thread overview]
Message-ID: <i1cv8j$446$1@dough.gmane.org> (raw)
In-Reply-To: <1278867705.15825.94.camel@lenovo.internal.reciva.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-07-10 19:01, Phil Blundell wrote:
> On Sun, 2010-07-11 at 15:45 +0200, Koen Kooi wrote:
>> Perl (among others) uses the 'LIBC' variable to point its linker to
>> libc.so.6, which fails due to OE redefing LIBC.
>>
>> Any objections to renaming LIBC to TARGET_LIBC in OE?
>
> How is perl getting to see that variable? I don't think it ought to be
> exported.
>
> I don't have any problem with renaming it, though I do wonder whether it
> would be better to just abolish it altogether in favour of inspecting
> ${HOST_OS}.
LIBC is currently used to set it for bitbake, e.g.:
MACHINE=beagleboard LIBC=eglibc bitbake foo
MACHINE=beagleboard LIBC=uclibc bitbake foo
Which also means we can't use any '_', so it would be TARGETLIBC or HOSTOS.
I'm not sure what the impact would be when we would unexport it, though.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMOgBTMkyGM64RGpERAqO9AJ4lSJbHDviQjgkIK5XkTC6/9voHIQCcDSrq
CK72iQi4N6rTh7x9hXt3jpM=
=XkZF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-11 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 13:45 'LIBC' variable clashes with perl variable Koen Kooi
2010-07-11 15:50 ` Tom Rini
2010-07-13 19:06 ` Tom Rini
2010-07-28 0:48 ` Tom Rini
2010-07-28 7:09 ` Koen Kooi
2010-07-28 7:24 ` Roman I Khimov
2010-07-11 17:01 ` Phil Blundell
2010-07-11 17:33 ` Koen Kooi [this message]
2010-07-11 22:17 ` Khem Raj
2010-07-11 22:39 ` Phil Blundell
2010-07-11 22:42 ` Khem Raj
2010-07-29 1:31 ` Tom Rini
2010-07-29 5:43 ` Roman I Khimov
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='i1cv8j$446$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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