From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: a5c7b007eaa675cc904f5285291d2f8a597efc84
Date: Thu, 10 Jan 2008 11:45:10 +0100 [thread overview]
Message-ID: <4785F736.5050707@student.utwente.nl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I just noticed a5c7b007eaa675cc904f5285291d2f8a597efc84 [1], which is a
bit bogus.
I've been building gcc 4.2.x for arm on my ubuntu gutsy machine for a
while now, and I can compile things like octave (which needs a fortran
compiler) and hope to be able to build R and grass soon (which also need
a fortran compiler). After this revision was committed bitbake halted to
a stop and informed me I needed to install gfortran. Hmmm.
I know for sure gfortran isn't need and I suspect the real issue is in
gmp-native or mpfr-native not being picked up correctly.
As a test I compiled gcc natively on my efika (without gfortran, but
with mpfr-dev and gmp-dev installed) and that works and now has a
working fortran compiler. I even compiled octave natively and it runs
quite well.
To sum it up:
~ * gfortran is NOT needed to build a gfortran cross-compiler, something
else is wrong.
regards,
Koen
[1]
http://lists.linuxtogo.org/pipermail/openembedded-commits/2008-January/011406.html
- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHhfc2MkyGM64RGpERAgDYAJ0a0kN10TFp3SlCv08riQk2NXZRHACgsBOU
hYdqF4j+KTr5ZkDOP1dZI/A=
=KswC
-----END PGP SIGNATURE-----
next reply other threads:[~2008-01-10 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 10:45 Koen Kooi [this message]
2008-01-10 11:21 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Holger Freyther
2008-01-10 11:46 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Koen Kooi
2008-01-10 11:51 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Philip Balister
2008-01-11 18:24 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Leon Woestenberg
2008-01-11 19:53 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Michael 'Mickey' Lauer
2008-01-11 20:05 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Leon Woestenberg
2008-01-12 0:02 ` a5c7b007eaa675cc904f5285291d2f8a597efc84 Paul Sokolovsky
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=4785F736.5050707@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.