From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits] Koen Kooi : gcc 4.3.3: fix regression from 4.3. 1 that caused fortran to get disabled for linux-gnueabi
Date: Thu, 14 May 2009 08:26:51 +0200 [thread overview]
Message-ID: <gugdje$d8p$1@ger.gmane.org> (raw)
In-Reply-To: <20090513211342.GN7973@smtp.west.cox.net>
On 13-05-09 23:13, Tom Rini wrote:
> On Wed, May 13, 2009 at 10:56:03PM +0200, GIT User account wrote:
>
>> Author: Koen Kooi<koen@openembedded.org>
>> Date: Wed May 13 22:49:19 2009 +0200
>>
>> gcc 4.3.3: fix regression from 4.3.1 that caused fortran to get disabled for linux-gnueabi
>
> This came up on IRC today for something else. Why do we only build a
> fortran compiler on ARM (EABI)? Should it just be disabled on a few
> platforms perhaps?
When we first started playing with things like this (2005-ish) some
people didn't want java, fortran or obj-c compilers, so everything
defaulted to off.
And gcc is crappy enough that java, fortran and objc just don't
crosscompile for every arch (check the arm fortran patches).
Having said that, I rather like complete toolchains, so if it was up to
me, java, fortran and objc would be turned on by default for every arch.
regards,
Koen
next prev parent reply other threads:[~2009-05-14 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090513205603.AAC121893A7@amethyst.openembedded.net>
2009-05-13 21:13 ` [oe-commits] Koen Kooi : gcc 4.3.3: fix regression from 4.3. 1 that caused fortran to get disabled for linux-gnueabi Tom Rini
2009-05-14 6:26 ` Koen Kooi [this message]
2009-05-14 8:06 ` Phil Blundell
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='gugdje$d8p$1@ger.gmane.org' \
--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.