Re: gnu-config-native and perl-native

[Tom Rini <tom_rini@mentor.com>]

On 06/01/2011 10:14 AM, Phil Blundell wrote:
> 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.

Probably a partial sync with oe.dev where we do have perl-native way up
front.

> 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?

It's never safe to use #!/full/random/path/to/bin/{perl,python,etc} in
things in our sysroots since some of us build in /very/deep/subdirs and
#! fails.

-- 
Tom Rini
Mentor Graphics Corporation