All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: 'LIBC' variable clashes with perl variable
Date: Wed, 28 Jul 2010 18:31:07 -0700	[thread overview]
Message-ID: <4C50D9DB.1070006@mentor.com> (raw)
In-Reply-To: <i1chst$tq5$1@dough.gmane.org>

Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> 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?

bitbake.conf: Unexport LIBC from the environment

As spoted by Koen at least perl makes use of LIBC coming from the 
environment to be meaningful, so don't export it as it doesn't match our 
meaning.

Signed-off-by: Tom Rini <tom_rini@mentor.com>

diff --git a/conf/bitbake.conf b/conf/bitbake.conf
index d523519..ddb6a79 100644
--- a/conf/bitbake.conf
+++ b/conf/bitbake.conf
@@ -799,3 +799,6 @@ TARGET_ARCH[unexport] = "1"
  # (breaks sysvinit at least)
  DISTRO[unexport] = "1"

+# Make sure that LIBC isn't exported
+# (breaks perl at least)
+LIBC[unexport] = "1"

-- 
Tom Rini
Mentor Graphics Corporation



  parent reply	other threads:[~2010-07-29  1:31 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
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 [this message]
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=4C50D9DB.1070006@mentor.com \
    --to=tom_rini@mentor.com \
    --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 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.