bitbake fsl-image-test failed

bitbake fsl-image-test failed

[Steven Grunza]

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

Has anyone tried to follow the instructions in 
https://community.freescale.com/docs/DOC-93844 called "How to test yocto 
for imx6" using 64-bit Ubuntu Quantal?

My quad sabre-lite board should be here today and I'm trying to get 
started with building the OS.  Sorry if this is a typical newbie issue 
but I'm kind of new building complete distributions.  I would much 
rather spend my time working on my application but my experience with 
eval boards has been that the SD card that is supposed to be included 
isn't and the company that sells the eval kit doesn't care once the sale 
has been made.  :(



My build failed with the following info:

| ERROR: Function failed: do_compile (see 
/home/yocto/rootfs_builder/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-cross-initial-4.7.2-r13/temp/log.do_compile.17913 
for further information)
ERROR: Task 506 
(/home/yocto/rootfs_builder/sources/poky/meta/recipes-devtools/gcc/gcc-cross-initial_4.7.bb, 
do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 300 tasks of which 63 didn't need to be 
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
/home/yocto/rootfs_builder/sources/poky/meta/recipes-devtools/gcc/gcc-cross-initial_4.7.bb, 
do_compile
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
grunzasr@stm32dbg:/home/yocto/rootfs_builder/build$
grunzasr@stm32dbg:/home/yocto/rootfs_builder/build$ uname -a
Linux stm32dbg 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
grunzasr@stm32dbg:/home/yocto/rootfs_builder/build$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.10
DISTRIB_CODENAME=quantal
DISTRIB_DESCRIPTION="Ubuntu 12.10"


grunzasr@stm32dbg:/home/yocto/rootfs_builder/build$ more 
/home/yocto/rootfs_builder/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-cross-initial-4.7.2-r13/temp/log.do_compile.17913

DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 
'bit-64', 'x86_64-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 ARCH_FLAGS_FOR_TARGET= -march=armv7-a -mthumb-interwork 
-mfloat-abi=softfp -mfpu=neon -mtune=cortex-a9 
-isystem/home/yocto/rootfs_builder
/build/tmp/sysroots/imx6qsabrelite/usr/include all-gcc all-target-libgcc
mkdir -p -- ./intl
mkdir -p -- ./libiberty
Configuring in ./intl
Configuring in ./libiberty
configure: creating cache ./config.cache
configure: creating cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles... no
checking for makeinfo... checking whether make sets $(MAKE)... makeinfo
checking for perl... perl
yes

[snip]

         /bin/sh 
/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/mkconfig.sh 
bconfig.h
gcc -c 
-isystem/home/yocto/rootfs_builder/build/tmp/sysroots/x86_64-linux/usr/include 
-O2 -pipe -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wno-narrowi
ng -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes 
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros 
-Wno-overlen
gth-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H 
-DGENERATOR_FILE -I. -Ibuild 
-I/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r
13/gcc-4.7.2/gcc 
-I/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/build 
-I/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-
4.7.2-r13/gcc-4.7.2/gcc/../include 
-I/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/../libcpp/include 
-I/home/yocto/rootfs_bui
lder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/../libdecnumber 
-I/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/../libd
ecnumber/dpd -I../libdecnumber    \
         -DBASEVER="\"4.7.2\"" -DDATESTAMP="\"\"" \
         -DREVISION="\"\"" \
         -DDEVPHASE="\"\"" -DPKGVERSION="\"(GCC) \"" \
         -DBUGURL="\"<http://gcc.gnu.org/bugs.html>\"" -o 
build/version.o 
/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/version
.c
/home/yocto/rootfs_builder/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/arm-poky-linux-gnueabi-as: 
unrecognized option '--64'
make[1]: *** [build/version.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/bin/sh 
/home/yocto/rootfs_builder/build/tmp/work-shared/gcc-4.7.2-r13/gcc-4.7.2/gcc/../move-if-change 
tmp-optionlist optionlist
echo timestamp > s-options
make[1]: Leaving directory 
`/home/yocto/rootfs_builder/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-cross-initial-4.7.2-r13/gcc-4.7.2/build.x86_64-l
inux.arm-poky-linux-gnueabi/gcc'
make: *** [all-gcc] Error 2
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (see 
/home/yocto/rootfs_builder/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/gcc-cross-initial-4.7.2-r13/temp/log.do_
compile.17913 for further information)


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

Re: bitbake fsl-image-test failed

[Daiane Angolini]

On 04/01/2013 11:32 AM, Steven Grunza wrote:
> Has anyone tried to follow the instructions in
> https://community.freescale.com/docs/DOC-93844 called "How to test yocto
> for imx6" using 64-bit Ubuntu Quantal?

I've been using 12.10 64-bits for a while without any problem so far


Please, use danny branch instead of master:

./repo init -b danny

And try again.

And I would say to you start using core-image-minimal only to make sure 
your build environment is OK


Daiane

Re: bitbake fsl-image-test failed

[Otavio Salvador]

On Mon, Apr 1, 2013 at 11:32 AM, Steven Grunza <steven.grunza@gmail.com> wrote:
> Has anyone tried to follow the instructions in
> https://community.freescale.com/docs/DOC-93844 called "How to test yocto for
> imx6" using 64-bit Ubuntu Quantal?

It should work fine however Yocto's master is having some heavy
changes for upcoming 1.4 release and it may break from time to time.

I'd suggest to you to remove your 'tmp' dir (inside of your build-dir)
and try to rebuild it doing a 'repo sync' and check if it works. For
now, the safest route is to stay at 'danny' as 'master' is a moving
target.

> My quad sabre-lite board should be here today and I'm trying to get started
> with building the OS.  Sorry if this is a typical newbie issue but I'm kind
> of new building complete distributions.  I would much rather spend my time
> working on my application but my experience with eval boards has been that
> the SD card that is supposed to be included isn't and the company that sells
> the eval kit doesn't care once the sale has been made.  :(

Yes; this happens sometimes. However board should work just fine with
the BSP we have here integrated so it should be more smooth :-)

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

bitbake fsl-image-gui fail

[Carrillodominguez Francisco Alberto-B35153]

Hello Yocto masters!

I tried today to compile my fsl-image-gui,  I had compiled before  other image that did not have gui.  So today I tried:

* repo sync
* bitbake fsl-image-sync

And I get this error when compiling libsoup:

| arm-poky-linux-gnueabi-libtool: link: arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a9 --sysroot=/home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd -O2 -pipe -g -feliminate-unused-debug-types -Wall -Wstrict-prototypes -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format=2 -Werror=missing-include-dirs -Werror=aggregate-return -Werror=declaration-after-statement -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -o .libs/range-test range-test.o test-utils.o  ../libsoup/.libs/libsoup-2.4.so /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libxml2.so -lm /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libgio-2.0.so /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libgmodule-2.0.so -ldl -lz -lresolv /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libgobject-2.0.so /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libgthread-2.0.so /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libffi.so /home/b35153/yocto/fsl-community-bsp/build/tmp/sysroots/imx6qsabresd/usr/lib/libglib-2.0.so -lpthread -lrt
| range-test.o: In function `main':
| /home/b35153/yocto/fsl-community-bsp/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libsoup-2.4-2.38.1-r1/libsoup-2.38.1/tests/range-test.c:351: undefined reference to `apache_init'
| collect2: error: ld returned 1 exit status
| make[2]: *** [range-test] Error 1
| make[2]: Leaving directory `/home/b35153/yocto/fsl-community-bsp/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libsoup-2.4-2.38.1-r1/libsoup-2.38.1/tests'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/b35153/yocto/fsl-community-bsp/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libsoup-2.4-2.38.1-r1/libsoup-2.38.1'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see /home/b35153/yocto/fsl-community-bsp/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libsoup-2.4-2.38.1-r1/temp/log.do_compile.9057 for further information)
ERROR: Task 5034 (/home/b35153/yocto/fsl-community-bsp/sources/poky/meta/recipes-support/libsoup/libsoup-2.4_2.38.1.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2719 tasks of which 2713 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:


Is this failing something known, or just that I should create a complete new folder and do everything from scratch instead of building on top of an old build.

Francisco C.