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.devel...@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.devel...@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.k...@gmail.com> wrote: >> >>> >>> On Apr 5, 2013, at 3:35 PM, Edward Vidal <vidal.devel...@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 >>> >> >> >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto