Bug 41309 - 4.4.1 build of fortran fails on T5140
Summary: 4.4.1 build of fortran fails on T5140
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 4.4.1
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-08 14:32 UTC by Ian James
Modified: 2009-09-21 10:04 UTC (History)
2 users (show)

See Also:
Host: sparc-sun-solaris2.10
Target: sparc-sun-solaris2.10
Build: sparc-sun-solaris2.10
Known to work:
Known to fail:
Last reconfirmed:


Attachments
file generated during build failure (10.28 KB, text/plain)
2009-09-08 14:39 UTC, Ian James
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian James 2009-09-08 14:32:10 UTC
after successful build & install 4.4.1 c,c++, attempt to build all languages fails with:
configure: error: GNU Fortran is not working; please report a bug in http://gcc.gnu.org/bugzilla

my config script is:
PATH=/usr/local/bin:$PATH
export PATH
CC=""
CFLAGS=""
unset CC
unset CFLAGS
../gcc-4.4.1/configure \
        --without-gnu-ld \
        --with-ld=/usr/ccs/bin/ld \
        --enable-shared
my make script is:
PATH=/usr/local/bin:$PATH
CC=""
CFLAGS=""
unset CC
unset CFLAGS
export PATH CC
make -j 40 $@

I will submit this and then see how to attach the detailed report 
./build/sparc-sun-solaris2.10/libgfortran/config.log
Comment 1 Ian James 2009-09-08 14:39:28 UTC
Created attachment 18542 [details]
file generated during build failure

The same result arises during make when configure is run without further options. The following SMC packages are installed on the system:
SMCgmp  SMClgcc346  SMCliconv  SMClintl  SMCmake  SMCmpfr  SMCnetsnmp  
SMCsed  SMCsudo  SMCtar  SUNWmgts  SUNWtsmc  
followed by s source build and install of mpfr-2.4.1
Comment 2 kargls 2009-09-08 14:55:16 UTC
(In reply to comment #1)
> Created an attachment (id=18542) [edit]
> file generated during build failure
> 
> The same result arises during make when configure is run without further
> options. The following SMC packages are installed on the system:
> SMCgmp  SMClgcc346  SMCliconv  SMClintl  SMCmake  SMCmpfr  SMCnetsnmp  
> SMCsed  SMCsudo  SMCtar  SUNWmgts  SUNWtsmc  
> followed by s source build and install of mpfr-2.4.1
> 

My first and only guess is that SMCmpfr and mpfr-2.4.1 are incompatible.
For example, configure is finding the library for mpfr-2.4.1 but the
build is finding the SMCmpfr header file.  Try using the --with-mpfr
configure option or remove one of the mpfr packages.  

PS: I note that you don't list a GMP package, but one must be present
if you built mpfr-2.4.1.  You may need/want to use the --with-gmp
option.
Comment 3 kargls 2009-09-08 14:56:37 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Created an attachment (id=18542) [edit]
> > file generated during build failure
> > 
> > The same result arises during make when configure is run without further
> > options. The following SMC packages are installed on the system:
> > SMCgmp  SMClgcc346  SMCliconv  SMClintl  SMCmake  SMCmpfr  SMCnetsnmp  
> > SMCsed  SMCsudo  SMCtar  SUNWmgts  SUNWtsmc  
> > followed by s source build and install of mpfr-2.4.1
> > 
> 
> PS: I note that you don't list a GMP package, but one must be present
> if you built mpfr-2.4.1.  You may need/want to use the --with-gmp
> option.

Whoops, well you list SMCgmp, sorry I missed that one.

Comment 4 Mikael Morin 2009-09-08 17:33:47 UTC
I suggest you clear your build directory and retry from scratch.
Comment 5 Ian James 2009-09-21 07:59:46 UTC
I separated the directories of Solaris packaged GNU (/usr/sfw), open built GNU (/usr/local) and locally built GNU components (usr/gnu) components, putting the built ones earlier in LD_LIBRARY_PATH and PATH. I then rebuilt from source using gcc-3.4.6 the packages mpfr, gmp. Then rebuilt gcc-4.4.1 and it has worked. Then rebuilt mpfr and gmp using gcc-4.4.1 which has all worked. 
Please mark the bug as user error.
Sorry for the false alert.    
Comment 6 Tobias Burnus 2009-09-21 10:04:03 UTC
(In reply to comment #5)
> Please mark the bug as user error.
> Sorry for the false alert.    

Great that it now works for you. (Closed as INVALID.)