failed build with current mercurial sources

Ben Abbott bpabbott at mac.com
Sun Mar 9 11:16:18 CDT 2008


On Mar 9, 2008, at 5:57 AM, Jaroslav Hajek wrote:

> On Sat, Mar 8, 2008 at 5:18 PM, Ben Abbott <bpabbott at mac.com> wrote:
>>
>> On Mar 8, 2008, at 5:08 AM, Jaroslav Hajek wrote:
>>
>>>>
>>>> I have access to an older Fedora 4 system with gcc 4.0.2 - I'll try
>>>> to
>>>> compile Octave there and reproduce the segfault.
>>>>
>>> I compiled Octave on a Fedora 4 Linux box with gcc/gfortran 4.0.2,  
>>> but
>>> the relevant qr test passes OK. Unless someone confirms the  
>>> problem on
>>> a different platform, I'm inclined to attribute it to a bug in
>>> gfortran 4.0.1.
>>
>> hmmm ... since I'm compiling with gfortran4.2.2, I assume our mean a
>> bug in gcc 4.0.1, or in gfortran 4.2.2?
>>
>
> So you're mixing two different gcc versions? Which libgcc_s does
> libcruft link to, the system version or the 4.2 version?

Unfortunately, don't know where to begin looking to answer that  
question.

How might I go about determining that?

Ben


More information about the Bug-octave mailing list