Bug 108766 – Workaround for Intel's fortran compiler's (ifc/ifort) bug about LANGUAGE env. variable

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Nicolas Bigaouette 2005-10-10 12:47:03 UTC]

Intel's fortran compiler (ifc/ifort) has a bug which prevent from running them
if the environment variable "LANGUAGE" is set. It fails with "Cannot find g++
location".

Reproducible: Always
Steps to Reproduce:
1.$ export LANGUAGE=testing
2.$ ifort -v
3.

Actual Results:  
Cannot find g++ location

Expected Results:  
Version 9.0

[Comment 1 Nicolas Bigaouette 2005-10-10 12:52:07 UTC]

Created attachment 70315 [details, diff]
Patches the ebuild and adds 2 files

Add 2 new files to the portage tree and modify the ebuild so it copy them to
the right place.

Those two files (/opt/intel/fortran90/bin/{ifc,ifort}) are just the script
running the compiler. Two lines have been added to them that uset the faulty
variables:
export -n IA32ROOT; unset IA32ROOT;
unset LANGUAGE

[Comment 2 Nicolas Bigaouette 2005-10-10 12:53:58 UTC]

This applies to dev-lang/ifc-9.0.021
(Intel Fortran 2003 compiler)

[Comment 3 Donnie Berkholz (RETIRED) 2005-10-10 16:52:34 UTC]

Why exactly would LANGUAGE be set anyway? Shouldn't that be LANG?

It also seems clear that if LANGUAGE affects the compiler, people might want the
compiler to be able to receive said variable instead of having a wrapper unset it.

[Comment 4 Donnie Berkholz (RETIRED) 2006-01-16 23:50:13 UTC]

Reassigning to proper maintainers.

[Comment 5 Sébastien Fabbro (RETIRED) 2007-11-15 20:53:33 UTC]

has been fixed in the ifc versions in the tree.