gcc enable-languages

gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

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?
Any and all help will be appreciated.
Thanks

[-- Attachment #2: Type: text/html, Size: 674 bytes --]

gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

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?
/home/vidal/POKY/build032713_panda/poky/meta/recipes-devtools/gcc/gcc-configure-common.inc
I changed the following

< LANGUAGES ?= "c,c++,fortran${JAVA}"

---

> LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
I am currently testing on a build for the  beagleboard and beaglebone
Any and all help will be appreciated.

[-- Attachment #2: Type: text/html, Size: 1405 bytes --]

Re: gcc enable-languages

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]


On Apr 5, 2013, at 8:51 AM, Edward Vidal <vidal.develone@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?


yes thats a bug, I think you can submit a patch for that. in order to enable it fully you also need to change gcc-configure-runtime.inc
add libgfortran to RUNTIMETARGET it would be nice if both knobs were turned on or off by one switch so you don't have to do it in two
different places but such is life

> /home/vidal/POKY/build032713_panda/poky/meta/recipes-devtools/gcc/gcc-configure-common.inc
> I changed the following 
> < LANGUAGES ?= "c,c++,fortran${JAVA}"
> ---
> > LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
> I am currently testing on a build for the  beagleboard and beaglebone
> Any and all help will be appreciated.
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #2: Type: text/html, Size: 2444 bytes --]

Re: gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 2943 bytes --]

Thanks now I get
Summary: 1 task failed:
  /home/vidal/POKY/build032713/poky/meta/recipes-devtools/gcc/
gcc-runtime_4.7.bb, do_configure
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
In the log this is what I see
ERROR: This autoconf log indicates errors, it looked at host include and/or
library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/home/vidal/POKY/build032713/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'
ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
/home/vidal/POKY/build032713/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp/log.do_configure.10792
NOTE: recipe gcc-runtime-4.7.2-r19: task do_configure: Failed
ERROR: Task 766
(/home/vidal/POKY/build032713/poky/meta/recipes-devtools/gcc/
gcc-runtime_4.7.bb, do_configure) failed with exit code '1'
Processing files:
kernel-modules-3.4.36+git0+80b4b5110dca5184b57e85f1e775fb006a2e85ad_c994390cfa28339cbc1ec3b56eeec83a5fa75bb7-r4.3.beagleboard
Processing files:
kernel-module-mailbox-mach-3.4.36+git0+80b4b5110dca5184b57e85f1e775fb006a2e85ad_c994390cfa28339cbc1ec3b56eeec83a5fa75bb7-r4.3.beagleboard
MACHINE=beaglebone bitbake -c clean gcc-runtime
Now I running MACHINE=beaglebone bitbake core-image-sato-sdk-ex -vDD




On Fri, Apr 5, 2013 at 11:00 AM, Khem Raj <raj.khem@gmail.com> wrote:

>
> On Apr 5, 2013, at 8:51 AM, Edward Vidal <vidal.develone@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?
>
>
>
> yes thats a bug, I think you can submit a patch for that. in order to
> enable it fully you also need to change gcc-configure-runtime.inc
> add libgfortran to RUNTIMETARGET it would be nice if both knobs were
> turned on or off by one switch so you don't have to do it in two
> different places but such is life
>
>
> /home/vidal/POKY/build032713_panda/poky/meta/recipes-devtools/gcc/gcc-configure-common.inc
> I changed the following
>
> < LANGUAGES ?= "c,c++,fortran${JAVA}"
>
> ---
>
> > LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
> I am currently testing on a build for the  beagleboard and beaglebone
> Any and all help will be appreciated.
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>

[-- Attachment #2: Type: text/html, Size: 4151 bytes --]

Re: gcc enable-languages

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]


On Apr 5, 2013, at 2:02 PM, Edward Vidal <vidal.develone@gmail.com> wrote:

> ERROR: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities.
> Rerun configure task after fixing this. The path was '/home/vidal/POKY/build032713/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'


so something is not cross compiling.

[-- Attachment #2: Type: text/html, Size: 2413 bytes --]

Re: gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

I believe that the error was in gcc-configure-common.inc it should of been
f95 not fortran. I am do a clean build  now for beagleboard and beaglebone.



On Fri, Apr 5, 2013 at 3:06 PM, Khem Raj <raj.khem@gmail.com> wrote:

>
> On Apr 5, 2013, at 2:02 PM, Edward Vidal <vidal.develone@gmail.com> wrote:
>
> ERROR: This autoconf log indicates errors, it looked at host include
> and/or library paths while determining system capabilities.
> Rerun configure task after fixing this. The path was
> '/home/vidal/POKY/build032713/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'
>
>
>
> so something is not cross compiling.
>

[-- Attachment #2: Type: text/html, Size: 2337 bytes --]

Re: gcc enable-languages

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 284 bytes --]


On Apr 5, 2013, at 3:35 PM, Edward Vidal <vidal.develone@gmail.com> wrote:

> I believe that the error was in gcc-configure-common.inc it should of been f95 not fortran. I am do a clean build  now for beagleboard and beaglebone.

No, f95 is old and deprecated 'fortran' is right

[-- Attachment #2: Type: text/html, Size: 1416 bytes --]

Re: gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

I went back to fortran but also changed FORTRAN ?= fortran
14,15c14,15
< FORTRAN ?= ",fortran"
< LANGUAGES ?= "c,c++,fortran${JAVA}"
---
> FORTRAN ?= ",f77"
> LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"


On Fri, Apr 5, 2013 at 5:00 PM, Khem Raj <raj.khem@gmail.com> wrote:

>
> On Apr 5, 2013, at 3:35 PM, Edward Vidal <vidal.develone@gmail.com> wrote:
>
> I believe that the error was in gcc-configure-common.inc it should of been
> f95 not fortran. I am do a clean build  now for beagleboard and beaglebone.
>
>
> No, f95 is old and deprecated 'fortran' is right
>

[-- Attachment #2: Type: text/html, Size: 1674 bytes --]

Re: gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 3428 bytes --]

 diff gcc-configure-common.inc gcc-configure-common.inc.orig
14c14
< FORTRAN ?= ",fortran"
---
> FORTRAN ?= ",f77"

| ERROR: Function failed: do_compile (see
/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp/log.do_compile.4820
for further information)
ERROR: Task 736
(/home/vidal/POKY/build032813_panda/poky/meta/recipes-devtools/gcc/
gcc-runtime_4.7.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3543 tasks of which 3542 didn't need to be
rerun and 1 failed.
No currently running tasks (426 of 6877)

Summary: 1 task failed:
  /home/vidal/POKY/build032813_panda/poky/meta/recipes-devtools/gcc/
gcc-runtime_4.7.bb, do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp

less log.do_compile.4820

home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran/../libgcc/unwind.h:68:54:
warning: unused parameter 'data' [-Wunused-parameter]
/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran/../libgcc/unwind.h:68:64:
warning: unused parameter 'compact' [-Wunused-parameter]
make[1]: *** [error.lo] Error 1

make[1]: *** [error.lo] Error 1
libtool: link: ( cd ".libs" && rm -f "libcaf_single.la" && ln -s "../
libcaf_single.la" "libcaf_single.la" )

libtool: link: ( cd ".libs" && rm -f "libcaf_single.la" && ln -s "../
libcaf_single.la" "libcaf_single.la" )
make[1]: *** [backtrace.lo] Error 1

make[1]: *** [backtrace.lo] Error 1
make[1]: Leaving directory
`/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'

make[1]: Leaving directory
`/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'
make: *** [all] Error 2

make: *** [all] Error 2
+ die 'oe_runmake failed'

+ die 'oe_runmake failed'
ERROR: Function failed: do_compile (see
/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp/log.do_compile.4820
for further information)



On Fri, Apr 5, 2013 at 5:07 PM, Edward Vidal <vidal.develone@gmail.com>wrote:

> I went back to fortran but also changed FORTRAN ?= fortran
> 14,15c14,15
> < FORTRAN ?= ",fortran"
>
> < LANGUAGES ?= "c,c++,fortran${JAVA}"
> ---
> > FORTRAN ?= ",f77"
>
> > LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
>
>
> On Fri, Apr 5, 2013 at 5:00 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
>>
>> On Apr 5, 2013, at 3:35 PM, Edward Vidal <vidal.develone@gmail.com>
>> wrote:
>>
>> I believe that the error was in gcc-configure-common.inc it should of
>> been f95 not fortran. I am do a clean build  now for beagleboard and
>> beaglebone.
>>
>>
>> No, f95 is old and deprecated 'fortran' is right
>>
>
>

[-- Attachment #2: Type: text/html, Size: 5448 bytes --]

Re: gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 3761 bytes --]

If I don't set libgfortran my image completes okay. When libgfortran in
gcc-config-runtime.inc I get do_compile error
On Apr 5, 2013 5:49 PM, "Edward Vidal" <vidal.develone@gmail.com> wrote:

>
>  diff gcc-configure-common.inc gcc-configure-common.inc.orig
> 14c14
> < FORTRAN ?= ",fortran"
> ---
> > FORTRAN ?= ",f77"
>
> | ERROR: Function failed: do_compile (see
> /home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp/log.do_compile.4820
> for further information)
> ERROR: Task 736
> (/home/vidal/POKY/build032813_panda/poky/meta/recipes-devtools/gcc/
> gcc-runtime_4.7.bb, do_compile) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 3543 tasks of which 3542 didn't need to be
> rerun and 1 failed.
> No currently running tasks (426 of 6877)
>
> Summary: 1 task failed:
>   /home/vidal/POKY/build032813_panda/poky/meta/recipes-devtools/gcc/
> gcc-runtime_4.7.bb, do_compile
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> /home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp
>
> less log.do_compile.4820
>
> home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran/../libgcc/unwind.h:68:54:
> warning: unused parameter 'data' [-Wunused-parameter]
> /home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran/../libgcc/unwind.h:68:64:
> warning: unused parameter 'compact' [-Wunused-parameter]
> make[1]: *** [error.lo] Error 1
>
> make[1]: *** [error.lo] Error 1
> libtool: link: ( cd ".libs" && rm -f "libcaf_single.la" && ln -s "../
> libcaf_single.la" "libcaf_single.la" )
>
> libtool: link: ( cd ".libs" && rm -f "libcaf_single.la" && ln -s "../
> libcaf_single.la" "libcaf_single.la" )
> make[1]: *** [backtrace.lo] Error 1
>
> make[1]: *** [backtrace.lo] Error 1
> make[1]: Leaving directory
> `/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'
>
> make[1]: Leaving directory
> `/home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/gcc-4.7.2/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/libgfortran'
> make: *** [all] Error 2
>
> make: *** [all] Error 2
> + die 'oe_runmake failed'
>
> + die 'oe_runmake failed'
> ERROR: Function failed: do_compile (see
> /home/vidal/POKY/build032813_panda/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-runtime/4.7.2-r19/temp/log.do_compile.4820
> for further information)
>
>
>
> On Fri, Apr 5, 2013 at 5:07 PM, Edward Vidal <vidal.develone@gmail.com>wrote:
>
>> I went back to fortran but also changed FORTRAN ?= fortran
>> 14,15c14,15
>> < FORTRAN ?= ",fortran"
>>
>> < LANGUAGES ?= "c,c++,fortran${JAVA}"
>> ---
>> > FORTRAN ?= ",f77"
>>
>> > LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
>>
>>
>> On Fri, Apr 5, 2013 at 5:00 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>
>>>
>>> On Apr 5, 2013, at 3:35 PM, Edward Vidal <vidal.develone@gmail.com>
>>> wrote:
>>>
>>> I believe that the error was in gcc-configure-common.inc it should of
>>> been f95 not fortran. I am do a clean build  now for beagleboard and
>>> beaglebone.
>>>
>>>
>>> No, f95 is old and deprecated 'fortran' is right
>>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 5995 bytes --]

Re: gcc enable-languages

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 277 bytes --]


On Apr 6, 2013, at 4:30 AM, Edward Vidal <vidal.develone@gmail.com> wrote:

> If I don't set libgfortran my image completes okay. When libgfortran in gcc-config-runtime.inc I get do_compile error
> 
> 

OK, did you try to run/build any fortran programs with this image.

[-- Attachment #2: Type: text/html, Size: 1030 bytes --]

Re: gcc enable-languages

[Dat Tran]

Edward Vidal <vidal.develone@...> writes:

> 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?
> Any and all help will be appreciated.
> Thanks


Hi Edward, 

I am having the same problem as you. Did you solve this issue. I am looking 
for gfortran recipe but I don't see it.

thanks

gcc enable-languages

[Edward Vidal]

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

*Dat Tran* dtran11 at
gmail.com<yocto%40yoctoproject.org?Subject=Re%3A%20%5Byocto%5D%20gcc%20enable-languages&In-Reply-To=%3Cloom.20130603T205457-413%40post.gmane.org%3E>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?
>* Any and all help will be appreciated.*>* Thanks*
Hi Edward,

I am having the same problem as you. Did you solve this issue. I am looking
for gfortran recipe but I don't see it.

thanks

They had recommended adding libgfortran to
poky/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
RUNTIMETARGET = "libssp libstdc++-v3 libgomp".  This did not work either,
If you find a solution I would be interested in getting the fix.
Thanks

[-- Attachment #2: Type: text/html, Size: 1368 bytes --]

Re: gcc enable-languages

[Dat Tran]

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?
> > Any and all help will be appreciated.
> > Thanks
> 
> Hi Edward, 
> 
> I am having the same problem as you. Did you solve this issue. I am 
looking 
> for gfortran recipe but I don't see it.
> 
> thanks
> They had recommended adding libgfortran to poky/meta/recipes-
devtools/gcc/gcc-configure-runtime.incRUNTIMETARGET = "libssp libstdc++-v3 
libgomp".  This did not work either,
> If you find a solution I would be interested in getting the fix.
> Thanks
> 
> 
> <div><div dir="ltr">
> <div>
> <div>Dat Tran 
>     <a href="mailto:yocto%40yoctoproject.org?
Subject=Re%3A%20%5Byocto%5D%20gcc%20enable-languages&amp;In-Reply-
To=%3Cloom.20130603T205457-413%40post.gmane.org%3E" title="[yocto] gcc 
enable-languages">dtran11 at gmail.com</a> wrote <br>&gt; Hello,
> &gt; I want to add support for FORTRAN in my image.
> &gt; On target gcc -v shows --enable-languages=c,c++
> &gt; This needs to --enable-languages=c,c++,fortran.based on my host 
system.
> &gt; How does the variable FORTRAN in 
> /home/vidal/POKY/build032813_panda/poky/meta/recipes-devtools/gcc/gcc-
> configure-common.inc get set?&nbsp; Can this be done in the local.conf 
file?
> &gt; 
> &gt; Does the FORTRAN ?= ",f77" this need to be FORTRAN ?= ",fortran" 
since we 
> are building gcc4.7?
> &gt; Any and all help will be appreciated.
> &gt; Thanks
> 
> Hi Edward, 
> 
> I am having the same problem as you. Did you solve this issue. I am 
looking 
> for gfortran recipe but I don't see it.
> 
> thanks
> They had recommended adding libgfortran to poky/meta/recipes-
devtools/gcc/gcc-configure-runtime.inc<br>RUNTIMETARGET = "libssp libstdc++-
v3 libgomp".&nbsp; This did not work either,<br>
> </div>If you find a solution I would be interested in getting the fix.<br>
> </div>Thanks<br><br>
> </div></div>
> 

Re: gcc enable-languages

[Paul Eggleton]

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

Re: gcc enable-languages

[Dat Tran]

Paul Eggleton <paul.eggleton@...> writes:

> 
> 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 <at> ...> 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, thanks for your suggestions. I think you are right in that there are 
more settings we need to set. Here is what I had done with no success:


diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc b/meta/recipes-
devtools/gcc/gcc-4.7.inc
index 1a3e09b..3c48232 100644
--- a/meta/recipes-devtools/gcc/gcc-4.7.inc
+++ b/meta/recipes-devtools/gcc/gcc-4.7.inc
@@ -82,7 +82,7 @@ S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}"
 B = "${WORKDIR}/gcc-${PV}/build.${HOST_SYS}.${TARGET_SYS}"
 
 # Language Overrides
-FORTRAN = ""
+FORTRAN = ",fortran"
 JAVA = ""
 
 EXTRA_OECONF_BASE = " --enable-lto \
diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc 
b/meta/recipes-devtools/gcc/gcc-configure-common.inc
index 4eb59fd..48dd606 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
@@ -10,7 +10,7 @@ JAVA_armeb ?= ""
 JAVA_mipsel ?= ""
 JAVA_sh3 ?= ""
 # gcc 3.x expects 'f77', 4.0 expects 'f95', 4.1 and 4.2 expect 'fortran'
-FORTRAN ?= ",f77"
+FORTRAN = ",fortran"
 LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
 # disable --enable-target-optspace for powerpc SPE
 # at -Os libgcc.so.1 creates references into
diff --git a/meta/recipes-devtools/gcc/gcc-configure-runtime.inc 
b/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
index d40383c..4c641f2 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
@@ -7,7 +7,7 @@ EXTRA_OECONF_PATHS = " \
     --with-sysroot=${STAGING_DIR_TARGET} \
     --with-build-sysroot=${STAGING_DIR_TARGET}"
 
-RUNTIMETARGET = "libssp libstdc++-v3"
+RUNTIMETARGET = "libgfortran libssp libstdc++-v3"
 RUNTIMETARGET_append_powerpc = " libgomp"
 RUNTIMETARGET_append_powerpc64 = " libgomp"
 #  ?

Re: gcc enable-languages

[Khem Raj]

On Jun 14, 2013, at 10:53 AM, Dat Tran <dtran11@gmail.com> wrote:

> Paul, thanks for your suggestions. I think you are right in that there are 
> more settings we need to set. Here is what I had done with no success:
> 
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc b/meta/recipes-
> devtools/gcc/gcc-4.7.inc
> index 1a3e09b..3c48232 100644
> --- a/meta/recipes-devtools/gcc/gcc-4.7.inc
> +++ b/meta/recipes-devtools/gcc/gcc-4.7.inc
> @@ -82,7 +82,7 @@ S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}"
> B = "${WORKDIR}/gcc-${PV}/build.${HOST_SYS}.${TARGET_SYS}"
> 
> # Language Overrides
> -FORTRAN = ""
> +FORTRAN = ",fortran"
> JAVA = ""
> 
> EXTRA_OECONF_BASE = " --enable-lto \
> diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc 
> b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> index 4eb59fd..48dd606 100644
> --- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
> +++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> @@ -10,7 +10,7 @@ JAVA_armeb ?= ""
> JAVA_mipsel ?= ""
> JAVA_sh3 ?= ""
> # gcc 3.x expects 'f77', 4.0 expects 'f95', 4.1 and 4.2 expect 'fortran'
> -FORTRAN ?= ",f77"
> +FORTRAN = ",fortran"
> LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
> # disable --enable-target-optspace for powerpc SPE
> # at -Os libgcc.so.1 creates references into
> diff --git a/meta/recipes-devtools/gcc/gcc-configure-runtime.inc 
> b/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
> index d40383c..4c641f2 100644
> --- a/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
> +++ b/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
> @@ -7,7 +7,7 @@ EXTRA_OECONF_PATHS = " \
>     --with-sysroot=${STAGING_DIR_TARGET} \
>     --with-build-sysroot=${STAGING_DIR_TARGET}"
> 
> -RUNTIMETARGET = "libssp libstdc++-v3"
> +RUNTIMETARGET = "libgfortran libssp libstdc++-v3"
> RUNTIMETARGET_append_powerpc = " libgomp"
> RUNTIMETARGET_append_powerpc64 = " libgomp"
> #  ?

ideally this is all you should need. But then its not frequent tested combination
What errors do you run into ?

Re: gcc enable-languages

[Dat Tran]

Khem Raj <raj.khem@...> writes:

> 
> 
> On Jun 14, 2013, at 10:53 AM, Dat Tran <dtran11@...> wrote:
> 
> > Paul, thanks for your suggestions. I think you are right in that there 
are 
> > more settings we need to set. Here is what I had done with no success:
> > 
> > 
> > diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc b/meta/recipes-
> > devtools/gcc/gcc-4.7.inc
> > index 1a3e09b..3c48232 100644
> > --- a/meta/recipes-devtools/gcc/gcc-4.7.inc
> > +++ b/meta/recipes-devtools/gcc/gcc-4.7.inc
> >  <at>  <at>  -82,7 +82,7  <at>  <at>  S = "${TMPDIR}/work-shared/gcc-
${PV}-${PR}/gcc-${PV}"
> > B = "${WORKDIR}/gcc-${PV}/build.${HOST_SYS}.${TARGET_SYS}"
> > 
> > # Language Overrides
> > -FORTRAN = ""
> > +FORTRAN = ",fortran"
> > JAVA = ""
> > 
> > EXTRA_OECONF_BASE = " --enable-lto \
> > diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc 
> > b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> > index 4eb59fd..48dd606 100644
> > --- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
> > +++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> >  <at>  <at>  -10,7 +10,7  <at>  <at>  JAVA_armeb ?= ""
> > JAVA_mipsel ?= ""
> > JAVA_sh3 ?= ""
> > # gcc 3.x expects 'f77', 4.0 expects 'f95', 4.1 and 4.2 expect 'fortran'
> > -FORTRAN ?= ",f77"
> > +FORTRAN = ",fortran"
> > LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
> > # disable --enable-target-optspace for powerpc SPE
> > # at -Os libgcc.so.1 creates references into
> > diff --git a/meta/recipes-devtools/gcc/gcc-configure-runtime.inc 
> > b/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
> > index d40383c..4c641f2 100644
> > --- a/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
> > +++ b/meta/recipes-devtools/gcc/gcc-configure-runtime.inc
> >  <at>  <at>  -7,7 +7,7  <at>  <at>  EXTRA_OECONF_PATHS = " \
> >     --with-sysroot=${STAGING_DIR_TARGET} \
> >     --with-build-sysroot=${STAGING_DIR_TARGET}"
> > 
> > -RUNTIMETARGET = "libssp libstdc++-v3"
> > +RUNTIMETARGET = "libgfortran libssp libstdc++-v3"
> > RUNTIMETARGET_append_powerpc = " libgomp"
> > RUNTIMETARGET_append_powerpc64 = " libgomp"
> > #  ?
> 
> ideally this is all you should need. But then its not frequent tested 
combination
> What errors do you run into ?
> 


This is the error I get:


configure: WARNING: unrecognized options: --disable-silent-rules, --with-
sysroot 
DEBUG: Shell function do_configure finished 
DEBUG: Executing python function do_qa_configure 
NOTE: Checking autotools environment for common misconfiguration 
ERROR: This autoconf log indicates errors, it looked at host include and/or 
library paths while determining system capabilities. 
Rerun configure task after fixing this. The path was 
'/home/appusr/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-
gnueabi/libtool-cross-2.4.2-r5.1/libtool-2.4.2' 
DEBUG: Python function do_qa_configure finished 
ERROR: Function failed: do_qa_configure 


Thanks

Re: gcc enable-languages

[Marcelo Valle]

Dat Tran <dtran11@...> writes:



> 
> This is the error I get:
> 
> configure: WARNING: unrecognized options: --disable-silent-rules, --with-
> sysroot 
> DEBUG: Shell function do_configure finished 
> DEBUG: Executing python function do_qa_configure 
> NOTE: Checking autotools environment for common misconfiguration 
> ERROR: This autoconf log indicates errors, it looked at host include 
and/or 
> library paths while determining system capabilities. 
> Rerun configure task after fixing this. The path was 
> '/home/appusr/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-
> gnueabi/libtool-cross-2.4.2-r5.1/libtool-2.4.2' 
> DEBUG: Python function do_qa_configure finished 
> ERROR: Function failed: do_qa_configure 
> 
> Thanks
> 
> 

Hello, 

I followed the same steps to use fortran with Yocto, but get a similar 
error:

ERROR: This autoconf log indicates errors, it looked at host include and/or 
library paths while determining system capabilities.
Rerun configure task after fixing this. The path was '/home/mvalle/poky-
dylan-9.0.0/build/tmp/work/x86_64-poky-linux/gcc-runtime/4.7.2-r19/gcc-
4.7.2/build.x86_64-poky-linux.x86_64-poky-linux/x86_64-poky-
linux/libgfortran'
ERROR: Function failed: do_qa_configure

You finally could fix this error?

Thanks in advance.

Re: gcc enable-languages

[Javi Roman]

I had the same issue. The problem seems the variable FC (Fortran
Compiler) is not properly setup (in meta/conf/bitbake.conf).

The libtool-cross recipe shows QA problems with wrong include paths
when uses x86_64-poky-linux-gfortran tests.

This workaround works for me:

recipes-devtools/gcc
└── gcc-cross_4.7.bbappend
recipes-devtools/libtool/
└── libtool-cross_2.4.2.bbappend

With:

$ cat recipes-devtools/gcc/gcc-cross_4.7.bbappend
FORTRAN = ",fortran"

$ cat recipes-devtools/libtool/libtool-cross_2.4.2.bbappend
export FC = "${CCACHE}${HOST_PREFIX}gfortran ${HOST_CC_ARCH}
--sysroot=${STAGING_DIR_HOST}"

Javi Roman


On Wed, Jul 24, 2013 at 1:39 PM, Marcelo Valle <mvalleavila@gmail.com> wrote:
> Dat Tran <dtran11@...> writes:
>
>
>
>>
>> This is the error I get:
>>
>> configure: WARNING: unrecognized options: --disable-silent-rules, --with-
>> sysroot
>> DEBUG: Shell function do_configure finished
>> DEBUG: Executing python function do_qa_configure
>> NOTE: Checking autotools environment for common misconfiguration
>> ERROR: This autoconf log indicates errors, it looked at host include
> and/or
>> library paths while determining system capabilities.
>> Rerun configure task after fixing this. The path was
>> '/home/appusr/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-
>> gnueabi/libtool-cross-2.4.2-r5.1/libtool-2.4.2'
>> DEBUG: Python function do_qa_configure finished
>> ERROR: Function failed: do_qa_configure
>>
>> Thanks
>>
>>
>
> Hello,
>
> I followed the same steps to use fortran with Yocto, but get a similar
> error:
>
> ERROR: This autoconf log indicates errors, it looked at host include and/or
> library paths while determining system capabilities.
> Rerun configure task after fixing this. The path was '/home/mvalle/poky-
> dylan-9.0.0/build/tmp/work/x86_64-poky-linux/gcc-runtime/4.7.2-r19/gcc-
> 4.7.2/build.x86_64-poky-linux.x86_64-poky-linux/x86_64-poky-
> linux/libgfortran'
> ERROR: Function failed: do_qa_configure
>
> You finally could fix this error?
>
> Thanks in advance.
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: gcc enable-languages

[Khem Raj]

On Aug 26, 2013, at 5:23 AM, Javi Roman <javiroman@kernel-labs.org> wrote:

> $ cat recipes-devtools/libtool/libtool-cross_2.4.2.bbappend
> export FC = "${CCACHE}${HOST_PREFIX}gfortran ${HOST_CC_ARCH}
> --sysroot=${STAGING_DIR_HOST}"

can you submit this as a patch to OE-Core libtool recipe please ?

gcc enable-languages

[Larry Baker]

See core-fortran.patch, "Fixes to build a gfortran cross compiler and the gfortran runtime libraries", which is an attachment at https://bugzilla.yoctoproject.org/show_bug.cgi?id=5091.  My bbappend files are there too.

Larry Baker
US Geological Survey
650-329-5608
baker@usgs.gov