From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gfortran needed on host to compile gcc >= 4.1.2
Date: Wed, 21 Nov 2007 20:12:59 -0600 [thread overview]
Message-ID: <4744E5AB.4040400@gmail.com> (raw)
In-Reply-To: <200711211347.58538.openembedded@haerwu.biz>
On 11/21/2007 06:47 AM, Marcin Juszkiewicz wrote:
> Dnia środa, 21 listopada 2007, Junqian Gordon Xu napisał:
>> I took the liberty to enable gfortran for gcc_4.1.2 (hence gcc >= 4.1.2
>> has fortran enabled). The side effect is that you need to install
>> gfortran or g77 on your host to compile it.
>
> Can I still build gcc(-cross) without gfortran when gfortran is not
> installed on host? If not they I would call it ugly regression...
I'm afraid you will get stuck in do_configure of gcc(-cross). I assume
the burden of installing gfortran on the host is low. But people may
disagree. Maybe we could introduce a fortran flag in a conf files, if
there is too much opposition to the change.
Regards
Gordon
next prev parent reply other threads:[~2007-11-22 4:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 9:32 gfortran needed on host to compile gcc >= 4.1.2 Junqian Gordon Xu
2007-11-21 12:47 ` Marcin Juszkiewicz
2007-11-22 2:12 ` Junqian Gordon Xu [this message]
2007-11-21 13:33 ` Esben Haabendal
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=4744E5AB.4040400@gmail.com \
--to=xjqian@gmail.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 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.