All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: gnu-config-native and perl-native
Date: Wed, 01 Jun 2011 18:14:27 +0100	[thread overview]
Message-ID: <1306948467.2529.162.camel@phil-desktop> (raw)

Further to my mini-crusade against perl-native, I discovered that it was
also being included during the initial pseudo build because
gnu-config-native depends on it.

This also seems a bit mysterious: gnu-config has:

DEPENDS_virtclass-native = "perl-native"

... which suggests that the dependency on perl-native was indeed
intentional rather than accidental.  But later, it has:

	# In the native case we want the system perl as perl-native can't have built yet
	if [ "${BUILD_ARCH}" != "${TARGET_ARCH}" ]; then
		sed -i -e 's,/usr/bin/env,${bindir}/env,g' ${D}${bindir}/gnu-configize
	fi

... which suggests that it isn't actually expecting to use the
newly-built perl anyway.  Does anybody know what's going on with that?

p.





             reply	other threads:[~2011-06-01 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 17:14 Phil Blundell [this message]
2011-06-01 17:20 ` gnu-config-native and perl-native Tom Rini
2011-06-01 17:51 ` Richard Purdie

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=1306948467.2529.162.camel@phil-desktop \
    --to=pb@pbcl.net \
    --cc=openembedded-core@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.