Bug 26647 – Having ARCH environment variable set spoils installation of linux-headers

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Jens-Uwe Mager 2003-08-14 16:42:06 UTC]

If the environment variable ARCH is set to some value the linux-headers ebuild
script fails to install the asm headers.

Reproducible: Always
Steps to Reproduce:
1. export ARCH=linux
2. emerge sys-kernel/linux-headers
3.

Actual Results:  
Other packages that need the asm parts of the headers fail to build.

Expected Results:  
The portage system should make sure that crucial environment variables are
cleaned out before building.

[Comment 1 Joshua Kinard 2003-10-22 21:40:14 UTC]

What ebuild/version of linux-headers have you tried this on?

If you haven't given it a shot, mind trying on the 2.4.21 ebuild and let
me know (via this bug) what happens?  2.4.21 uses kernel.eclass (/usr/portage/eclass/),
and It is possible a fix can be implemented there or in the ebuilds.

[Comment 2 Jens-Uwe Mager 2003-10-24 08:38:20 UTC]

Even the 2.4.21 ebuild uses $ARCH in the script and does not like if ARCH
is set to anything else.

[Comment 3 Joshua Kinard 2003-10-24 08:56:07 UTC]

In the 2.4.21 ebuild, what about changing:

ARCH="${ARCH:-`uname -m`}"

to

ARCH="${uname -m}"?


How does that work for you?

[Comment 4 Jens-Uwe Mager 2003-10-24 09:05:16 UTC]

This is fine, it avoids nasty surprises.

[Comment 5 Joshua Kinard 2003-10-29 15:10:01 UTC]

This is more up my alley, so I'll take care of this bug shortly.

[Comment 6 Joshua Kinard 2003-10-30 15:18:23 UTC]

Fixed and in CVS.  Let me know if the issue somehow continues to persist.