From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Dat Tran <dtran11@gmail.com>, Edward Vidal <vidal.develone@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: gcc enable-languages
Date: Fri, 14 Jun 2013 17:35:08 +0100 [thread overview]
Message-ID: <1571616.VWc8oWtlLJ@helios> (raw)
In-Reply-To: <loom.20130614T060308-378@post.gmane.org>
On Friday 14 June 2013 04:04:07 Dat Tran wrote:
> Anyone know of any clues that will help us? Thanks.
>
> Edward Vidal <vidal.develone@...> writes:
> > Dat Tran <dtran11 at gmail.com> wrote
> > > Hello,
> > >
> > > I want to add support for FORTRAN in my image.
> > > On target gcc -v shows --enable-languages=c,c++
> > > This needs to --enable-languages=c,c++,fortran.based on my host system.
> > > How does the variable FORTRAN in
> >
> > /home/vidal/POKY/build032813_panda/poky/meta/recipes-devtools/gcc/gcc-
> > configure-common.inc get set? Can this be done in the local.conf file?
> >
> > > Does the FORTRAN ?= ",f77" this need to be FORTRAN ?= ",fortran" since
> > > we are building gcc4.7?
I have no direct knowledge of how to enable language support, but if you look
at meta/recipes-devtools/gcc/gcc-4.7.inc you'll see it sets FORTRAN = "",
which means setting it with = in local.conf won't work (since local.conf
parsing comes before recipes) nor will the FORTRAN ?= setting in meta/recipes-
devtools/gcc/gcc-configure-common.inc.
I'd suggest bbappending the appropriate gcc recipe and set FORTRAN there
(which one depends on where you want to compile fortran code; gcc-cross would
be the right one for building a recipe for fortran software to run on the
target). You may need to set other variables in the bbappend as well, I'm not
entirely sure.
An example of a layer that does something similar would be the meta-ada layer:
https://github.com/Lucretia/meta-ada
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-14 16:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 20:33 gcc enable-languages Edward Vidal
2013-06-14 4:04 ` Dat Tran
2013-06-14 16:35 ` Paul Eggleton [this message]
2013-06-14 17:53 ` Dat Tran
2013-06-14 18:00 ` Khem Raj
2013-06-14 18:03 ` Dat Tran
2013-07-24 11:39 ` Marcelo Valle
2013-08-26 12:23 ` Javi Roman
2013-08-27 16:25 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2013-08-31 7:16 Larry Baker
2013-04-05 15:51 Edward Vidal
2013-04-05 17:00 ` Khem Raj
2013-04-05 21:02 ` Edward Vidal
2013-04-05 21:06 ` Khem Raj
2013-04-05 22:35 ` Edward Vidal
2013-04-05 23:00 ` Khem Raj
2013-04-05 23:07 ` Edward Vidal
2013-04-05 23:49 ` Edward Vidal
2013-04-06 11:30 ` Edward Vidal
2013-04-06 14:51 ` Khem Raj
2013-04-04 17:28 Edward Vidal
2013-06-03 18:56 ` Dat Tran
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=1571616.VWc8oWtlLJ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dtran11@gmail.com \
--cc=vidal.develone@gmail.com \
--cc=yocto@yoctoproject.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.