Bug 49438 - error during make
Summary: error during make
Status: RESOLVED WORKSFORME
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 4.5.3
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-16 12:53 UTC by eisoab
Modified: 2011-11-07 22:48 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2011-07-24 18:41:44


Attachments
config.log (8.08 KB, text/x-log)
2011-06-16 12:53 UTC, eisoab
Details

Note You need to log in before you can comment on or make changes to this bug.
Description eisoab 2011-06-16 12:53:25 UTC
Created attachment 24545 [details]
config.log

make ends with 

checking whether the GNU Fortran compiler is working... no
configure: error: GNU Fortran is not working; please report a bug in http://gcc.gnu.org/bugzilla, attaching /home/e.ab/software/src/gcc-4.5.3-build/i686-pc-linux-gnu/libgfortran/config.log
make[1]: *** [configure-target-libgfortran] Error 1
make[1]: Leaving directory `/data1/software/src/gcc-4.5.3-build'
make: *** [all] Error 2


config.log attached...

-E
Comment 1 Tobias Burnus 2011-06-16 13:39:34 UTC
In 95% of the cases one sees this error, there is a problem with GMP or MPFR.

That seems to be also the case here:

/home/e.ab/software/src/gcc-4.5.3-build/./gcc/f951: symbol lookup error: /usr/local/lib/libmpfr.so.1: undefined symbol: __gmp_get_memory_functions


Can you check that your GMP and MPFR are compatible, that they are in the library search path, etc.?
Comment 2 kargls 2011-06-16 16:31:23 UTC
(In reply to comment #0)
> Created attachment 24545 [details]
> config.log
> 
> make ends with 
> 
> checking whether the GNU Fortran compiler is working... no
> configure: error: GNU Fortran is not working; please report a bug in
> http://gcc.gnu.org/bugzilla, attaching
> /home/e.ab/software/src/gcc-4.5.3-build/i686-pc-linux-gnu/libgfortran/config.log
> make[1]: *** [configure-target-libgfortran] Error 1
> make[1]: Leaving directory `/data1/software/src/gcc-4.5.3-build'
> make: *** [all] Error 2
> 

What is the configure command line you used to configure
the gcc?
Comment 3 eisoab 2011-06-16 17:36:15 UTC
kargl at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49438
>
> kargl at gcc dot gnu.org changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |kargl at gcc dot gnu.org
>
> --- Comment #2 from kargl at gcc dot gnu.org 2011-06-16 16:31:23 UTC ---
> (In reply to comment #0)
>    
>> Created attachment 24545 [details]
>> config.log
>>
>> make ends with
>>
>> checking whether the GNU Fortran compiler is working... no
>> configure: error: GNU Fortran is not working; please report a bug in
>> http://gcc.gnu.org/bugzilla, attaching
>> /home/e.ab/software/src/gcc-4.5.3-build/i686-pc-linux-gnu/libgfortran/config.log
>> make[1]: *** [configure-target-libgfortran] Error 1
>> make[1]: Leaving directory `/data1/software/src/gcc-4.5.3-build'
>> make: *** [all] Error 2
>>
>>      
> What is the configure command line you used to configure
> the gcc?
>
>    
nothing. just ../configure

there was a gmp version on the machine that was too old and no mpfr

I unpacked the latest source tar files of gmp and mpfr in  the
source directory (gcc-4.5.3) hoping that they would be found an installed.

But after make distclean  ;  ../gcc-4.5.3/configure
make  ends with the same error as before. (although i didn't compare the 
config.log
it was overwritten)

I'm now first installing gmp and mpfr by hand.
I probably have to remove the old gmp version right?


Eiso
Comment 4 Steve Kargl 2011-06-16 17:52:39 UTC
On Thu, Jun 16, 2011 at 05:36:35PM +0000, eisoab at gmail dot com wrote:
> 
> > What is the configure command line you used to configure
> > the gcc?
> >
> >    
> nothing. just ../configure
> 

This appears to mean that you are trying to build
gcc within its source tree.  That is not support.
Please the instructions for building gcc.

>
> I probably have to remove the old gmp version right?
> 

This would certainly ensure that the old versions are
not found and used.
Comment 5 eisoab 2011-06-16 17:56:10 UTC
sgk at troutmask dot apl.washington.edu wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49438
>
> --- Comment #4 from Steve Kargl<sgk at troutmask dot apl.washington.edu>  2011-06-16 17:52:39 UTC ---
> On Thu, Jun 16, 2011 at 05:36:35PM +0000, eisoab at gmail dot com wrote:
>>
>>> What is the configure command line you used to configure
>>> the gcc?
>>>
>>>
>> nothing. just ../configure
sorry that was incorrect, I meant

../gcc-4.5.3/configure

I'm using a gcc-4.5.3-build dir next to gcc-4.5.3

Eiso

>>
>
> This appears to mean that you are trying to build
> gcc within its source tree.  That is not support.
> Please the instructions for building gcc.
>
>>
>> I probably have to remove the old gmp version right?
>>
>
> This would certainly ensure that the old versions are
> not found and used.
>
Comment 6 eisoab 2011-06-16 18:07:41 UTC
Eiso AB wrote:
> sgk at troutmask dot apl.washington.edu wrote:
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49438
>>
>> --- Comment #4 from Steve Kargl<sgk at troutmask dot
>> apl.washington.edu> 2011-06-16 17:52:39 UTC ---
>> On Thu, Jun 16, 2011 at 05:36:35PM +0000, eisoab at gmail dot com wrote:
>>>
>>>> What is the configure command line you used to configure
>>>> the gcc?
>>>>
>>>>
>>> nothing. just ../configure
> sorry that was incorrect, I meant
>
> ../gcc-4.5.3/configure
>
> I'm using a gcc-4.5.3-build dir next to gcc-4.5.3
>
> Eiso
>
>>>
>>
>> This appears to mean that you are trying to build
>> gcc within its source tree. That is not support.
>> Please the instructions for building gcc.
>>
>>>
>>> I probably have to remove the old gmp version right?
>>>
>>
>> This would certainly ensure that the old versions are
>> not found and used.

yum wants to remove about 60 packages when I try that. So I
think I'll leave that one alone.

-E



>>
>
Comment 7 Daniel Franke 2011-07-24 18:41:44 UTC
Set to waiting. Close if no additional info shows up in a reasonable time frame.
Comment 8 Francois-Xavier Coudert 2011-11-07 22:47:04 UTC
Closing, please reopen with detailed information if you still encounter the issue. One problem may be that you were compiling with recent GMP headers, but picking up an older GMP library at runtime.
Comment 9 Francois-Xavier Coudert 2011-11-07 22:48:26 UTC
Closing, please reopen with detailed information if you still encounter the issue. One problem may be that you were compiling with recent GMP headers, but picking up an older GMP library at runtime.