From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: fortran and octave
Date: Tue, 18 Sep 2007 20:49:42 +0200 [thread overview]
Message-ID: <46F01DC6.6000503@student.utwente.nl> (raw)
In-Reply-To: <46F01466.4080000@dominion.kabel.utwente.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Koen Kooi schreef:
> Alain2210 schreef:
>> Hello,
>>
>> I would like to bitbake octave for org.openembedded.dev.
>> But octave needs fortran ou f2c.
>> It seems that fortran has been remove from gcc-cross_4.1.2.bb (or perhaps
>> before).
>> So I have tried to
>> 1) add fortran in gcc-cross_4.1.2.bb but I get an error.
>> 2) compile octave with f2c without success. (even with the f2c of the host)
>>
>> So what is the good way to compile octave and/or fortran and/or f2c ?
>
> For gcc 3.4 through 4.1.x fortran is broken for arm (gcc ICEs on compiling gcc), Lennert
> Buytenhek had some patches for it, I don't know if they fix and and if yes, I don't know
> if they are in 4.2.1. I'm firing of a build of 4.2.1 with fortran enabled anyway :)
Same old, same old:
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:
In function 'specific__mod_i8':
/media/hda4/OE/build/tmp-new/angstrom/work/armv5te-angstrom-linux-uclibcgnueabi/gcc-cross-4.2.1-r4/gcc-4.2.1/libgfortran/generated/_mod_i8.F90:42:
internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFG8B3GMkyGM64RGpERAqU7AKCp1z6hELV18erP+dMbhPayd/GhxgCcDMcN
+3tocngg8sZuIC30inMy5SM=
=xCvQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-09-18 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 17:54 fortran and octave Alain2210
2007-09-18 18:09 ` Koen Kooi
2007-09-18 18:29 ` Alain2210
2007-09-18 18:49 ` Koen Kooi [this message]
2007-09-18 19:04 ` Alain2210
2007-09-18 21:34 ` Alain2210
2007-09-19 8:55 ` Alain2210
2007-09-19 10:23 ` Koen Kooi
2007-09-19 10:47 ` Alain2210
2007-09-19 11:10 ` Koen Kooi
2007-09-20 9:16 ` Alain2210
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=46F01DC6.6000503@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.