From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: fortran problem on hardy build machine (gcc-cross fails do_compile)
Date: Wed, 10 Jun 2009 17:18:27 +0100 [thread overview]
Message-ID: <1244650707.21585.72.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <h0ok27$3ue$1@ger.gmane.org>
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
next prev parent reply other threads:[~2009-06-10 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 15:38 fortran problem on hardy build machine (gcc-cross fails do_compile) Rolf Leggewie
2009-06-10 16:18 ` Phil Blundell [this message]
2009-06-11 9:17 ` Rolf Leggewie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244650707.21585.72.camel@mill.internal.reciva.com \
--to=pb@reciva.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox