fortran problem on hardy build machine (gcc-cross fails do_compile)

fortran problem on hardy build machine (gcc-cross fails do_compile)

[Rolf Leggewie]

Hi,

I've been struggling with gcc-cross failing do_compile on my hardy build
machine for about half a year now.  It has something to do with fortran.
I have installed every fortran package I could find in aptitude, yet
the issue is unresolved.  I'd appreciate if you'd take a look at the
compile log in http://oss.leggewie.org/oe/gcc-cross-4.3.3-r4.1/temp/ and
let me know if you have any suggestion.

Regards

Rolf

Re: fortran problem on hardy build machine (gcc-cross fails do_compile)

[Phil Blundell]

The error message contains good advice:

configure: error: GNU Fortran is not working; please report a bug [...]
attaching /export/oe/tmp/angstrom/org.openembedded.dev/work/armv5te-angstrom-linux-gnueabi/gcc-cross-4.3.3-r4.1/gcc-4.3.3/build.i686-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgfortran/config.log

What does the config.log file in question say?

p.

On Thu, 2009-06-11 at 00:38 +0900, Rolf Leggewie wrote:
> Hi,
> 
> I've been struggling with gcc-cross failing do_compile on my hardy build
> machine for about half a year now.  It has something to do with fortran.
> I have installed every fortran package I could find in aptitude, yet
> the issue is unresolved.  I'd appreciate if you'd take a look at the
> compile log in http://oss.leggewie.org/oe/gcc-cross-4.3.3-r4.1/temp/ and
> let me know if you have any suggestion.
> 
> Regards
> 
> Rolf
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: fortran problem on hardy build machine (gcc-cross fails do_compile)

[Rolf Leggewie]

Phil Blundell wrote:
> What does the config.log file in question say?

http://oss.leggewie.org/oe/gcc-cross-4.3.3-r4.1/gcc-4.3.3/build.i686-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgfortran/config.log 
says a lot, I guess. But I don't understand much of it.