Issue 12246

Summary: configure script incorrectly sets path in LinuxIntelEnv.Set when alternative compiler is used
Product: utilities Reporter: simonbr
Component: codeAssignee: foskey
Status: CLOSED DUPLICATE QA Contact: Unknown <non-migrated>
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 1.0.2   
Target Milestone: ---   
Hardware: Other   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description simonbr 2003-03-11 20:09:15 UTC 
On SuSE 8.1 (gcc 3.2(sic)) the first time the C compiler is called in the    
bootstrap script, an internal compiler error occurs. Therefore, I installed  
GCC 3.2.1 as that compiler version had been reported to work.    
I put its location /opt/gcc3.2.1/bin in my PATH and ran the configure script. 
The configure script recognized this compiler, but I still got the same error 
in bootstrap, because in LinuxIntelEnv.Set the PATH was  
set with /usr/bin *before* /opt/gcc3.2.1, so that the wrong compiler was still 
executed.   
After changing the order in LinuxIntelEnv.Set the bootstrap completed without  
errors.
Comment 1 foskey 2003-03-17 01:39:44 UTC 
Temporary work around is to run:

CC=opt/gcc3.2.1/bin/gcc
CXX=opt/gcc3.2.1/bin/g++
export CC
export CXX
./configure

Regariding the core problem this is a duplicate issue. I will find 
issue and mark it as duplicate.
Comment 2 foskey 2003-03-18 11:04:27 UTC 
This is because the paths are set in the wrong order.

*** This issue has been marked as a duplicate of 8181 ***
Comment 3 foskey 2003-07-31 02:38:29 UTC 
Closing reopen if there is any further.
Comment 4 SVN Robot 2013-05-08 09:43:03 UTC 
"alg" committed SVN revision 1480203 into trunk:
i12246 Corrected three basic problems in the metafile breaker