I get the following errors when building meta-toolchain-qt5 with the latest from https://github.com/mahyar-ym/boundary-community-bsp-base
meta-qt5 is using qt 5.3.
I've attached the files bblayers.conf and local.confg.
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3475: $? = 0
configure:3464: i686-pokysdk-linux-gcc -march=i686 --sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux -v >&5
Using built-in specs.
COLLECT_GCC=i686-pokysdk-linux-gcc
COLLECT_LTO_WRAPPER=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/lto-wrapper
Target: i686-pokysdk-linux
Configured with: /home/opti/sandbox/mahyar-ym/build/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/configure --build=x86_64-linux --host=x86_64-linux --target=i686-pokysdk-linux --prefix=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr --exec_prefix=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr --bindir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/bin/i686-pokysdk-linux --sbindir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/bin/i686-pokysdk-linux --libexecdir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux --datadir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/share --sysconfdir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/etc --sharedstatedir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/com --localstatedir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/var --libdir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/lib/i686-pokysdk-linux --includedir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/include --oldincludedir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/include --infodir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/share/info --mandir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux --enable-clocale=generic --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=i686-pokysdk-linux- --without-local-prefix --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libmudflap --with-system-zlib --with-linker-hash-style=gnu --enable-linker-build-id --with-ppl=no --with-cloog=no --enable-checking=release --enable-cheaders=c_global --with-gxx-include-dir=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/i686-nativesdk-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/usr/include/c++/4.9.1 --with-sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/i686-nativesdk-pokysdk-linux --with-build-sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/i686-nativesdk-pokysdk-linux --enable-poison-system-directories --with-mpfr=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr --with-system-zlib --disable-nls --enable-__cxa_atexit
Thread model: posix
gcc version 4.9.1 (GCC)
configure:3475: $? = 0
configure:3464: i686-pokysdk-linux-gcc -march=i686 --sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux -V >&5
i686-pokysdk-linux-gcc: error: unrecognized command line option '-V'
i686-pokysdk-linux-gcc: fatal error: no input files
compilation terminated.
configure:3475: $? = 1
configure:3464: i686-pokysdk-linux-gcc -march=i686 --sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux -qversion >&5
i686-pokysdk-linux-gcc: error: unrecognized command line option '-qversion'
i686-pokysdk-linux-gcc: fatal error: no input files
compilation terminated.
configure:3475: $? = 1
configure:3495: checking whether the C compiler works
configure:3517: i686-pokysdk-linux-gcc -march=i686 --sysroot=/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux -isystem/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/usr/include -O2 -pipe -D_GNU_SOURCE -isystem/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/usr/include -L/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/usr/lib -Wl,-rpath-link,/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/usr/lib -Wl,-rpath,/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/usr/lib -Wl,-O1 -L/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/lib -Wl,-rpath-link,/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/lib -Wl,-rpath,/opt/poky/1.6+snapshot/sysroots/i686-pokysdk-linux/lib -Wl,-O1 conftest.c >&5
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crt1.o: No such file or directory
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crti.o: No such file or directory
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crtbegin.o: No such file or directory
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc_s
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lc
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc_s
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crtend.o: No such file or directory
/home/opti/sandbox/mahyar-ym/build/tmp/sysroots/x86_64-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:3521: $? = 1
configure:3559: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define PACKAGE "alsa-lib"
| #define VERSION "1.0.27.2"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3564: error: in `/home/opti/sandbox/mahyar-ym/build/tmp/work/cortexa9hf-vfp-neon-mx6-pokysdk-linux/nativesdk-alsa-lib/1.0.27.2-r0/build':
configure:3566: error: C compiler cannot create executables
Original Attachment has been moved to: local.conf.zip
Original Attachment has been moved to: bblayers.conf.zip
Hello,
I do have exactly the same problem, using ubuntu 14.04 with freescale yocto master
The same fail when nativesdk-alsa-lib is configuring ...
When i look into the config.log I also see :
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crt1.o: No such file or directory
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crti.o: No such file or directory
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crtbegin.o: No such file or directory
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc_s
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lc
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find -lgcc_s
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crtend.o: No such file or directory
tmp/sysroots/i686-linux/usr/libexec/i686-pokysdk-linux/gcc/i686-pokysdk-linux/4.9.1/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
I am wondering if it is normal that it compiles nativesdk-alsa-lib into tmp/work/cortexa9hf-vfp-neon-mx6-pokysdk-linux/ ?
Thank you ...
I have the same issue
| checking for x86_64-pokysdk-linux-gcc... x86_64-pokysdk-linux-gcc --sysroot=/home/gauthier/numpy-fsl-community-bsp/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux
| checking whether the C compiler works... no
| configure: error: in `/home/gauthier/numpy-fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-mx6-pokysdk-linux/nativesdk-alsa-lib/1.0.27.2-r0/build':
| configure: error: C compiler cannot create executables
1. it is looking for a x86_64 compiler, while I am targeting an i.MX6.
2. the sysroot argument looks at cortexa9hf-vfp-neon-mx6-pokysdk-linux while for my target it should be imx6qsabresd (I think. That's where the images are usually placed.)
At the top of the log, I see this:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common']
and this:
| NOTE: Executing ACLOCAL="aclocal --system-acdir=/home/gauthier/numpy-fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-mx6-pokysdk-linux/nativesdk-alsa-lib/1.0.27.2-r0/build/aclocal-copy/" autoreconf --verbose --install --force --exclude=autopoint -I /home/gauthier/numpy-fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-mx6-pokysdk-linux/nativesdk-alsa-lib/1.0.27.2-r0/alsa-lib-1.0.27.2/m4/ -I /home/gauthier/numpy-fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-mx6-pokysdk-linux/nativesdk-alsa-lib/1.0.27.2-r0/alsa-lib-1.0.27.2/utils/
Isn't is a little strange that it is trying to work in cortexa9hf, when my images usually get stored in imx6sabresd?
Otavio,
Thanks for fixing the compile issue with alsa. Your changes worked and got me past the original problem. However, there are two other issues that exist with the configuration I am using (this may need to be put in a separate thread).
The following is the process I followed and the repostories where I got the files (see attached file "build-28Aug14" for details).
cd sandbox
mkdir mahyar-ym
cd mahyar-ym
curl https://storage.googleapis.com/git-repo-downloads/repo > repo
chmod a+x repo
Get Freescale
./repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master
./repo sync
cd sources
Get meta-boundary
git clone -b master https://github.com/mahyar-ym/meta-boundary.git
Get meta-qt5
git clone -b master https://github.com/meta-qt5/meta-qt5.git
Remove browser from Boundary devices
cd meta-boundary
rm -rf recipes-browser
cd ../..
Removed the following from meta-fsl-arm (don't know if this is necessary but saw it in the post "Qt 5.3.0 release on i.MX6 using fsl-community-bsp and meta-qt5"):
meta-fsl-arm/qt5-layer/recipes-qt/qt5/qtmultimedia_%.bbappend
Initialize environment
MACHINE=nitrogen6x . setup-environment build
Add the following to the end of BBLAYERS in bblayers.conf
${BSPDIR}/sources/meta-qt5 \
${BSPDIR}/sources/meta-boundary \
Edit local.conf
See attached “local.conf”.
Build Tool chain
bitbake meta-toolchain-qt5
It will fail the first time on the multimedia gsttools.
Manually applied the changes from the attached file "multimedia.patch" which came from the following site.
bitbake meta-toolchain-qt5
failed due to PACKAGE_ARCH error - see attached build log.
Had to do: bitbake -c cleanall meta-toolchain-qt5
bitbake meta-toolchain-qt5
tool chain was built successfully.
Build Image
bitbake core-image-minimal
failed due to PACKAGE_ARCH error - see attached build log.
Had to do: bitbake -c cleanall meta-toolchain-qt5
bitbake core-image-minimal
image was built successfully
Hi James,
Bryan has reached out to us, and we haven't had a chance to try and reproduce this (we're hardly Yocto experts).
My best guess here is that the problem stems from an order-of-events thing.
As I understand it, before building the toolchain (meta-toolchain-qt5), you first need to build an image with the run-time components, so that the toolchain build knows which headers, libraries, and such to include in the development environment.
bryan.prather@optimedical.com, did you build the run-time image successfully first? Your local.conf seems to include the "dev-pkgs" feature (I think that's needed).
I did build the core-image-minimal before building the tool chain.
Hello bryan.prather@optimedical.com
One thing I noticed from your platform description is that you are using master. We had some hard time in master these days and we're still recovering from it ;-)
The meta-toolchain-qt5 ought to be self-contained so you don't need to build any recipe before building it.
So now back to the topic, it seems you have a broken sysroot as the core libraries from GCC and GlibC are missing.
In this situation the easiest is to start over; so remove your tmp directory and start a new plain build. If it still fails, drop the sstate-cache and tmp directory. In stable branches this is very rare to be necessary as metadata is stable but in master those surprises happen from time to time.
Otavio - thanks for your response.
What branch should I use if not master?
I did remove the tmp directory and everything in the build directory except for the conf directory. The problem still exists.
daisy branch.
I deleted everything and got the boundary devices master branch from (no daisy branch available) https://github.com/mahyar-ym/boundary-community-bsp-base. I deleted the meta-qt5 in the sources directory and replaced it with the daisy branch as follows (I don't know if this is valid):
"git clone -b daisy https://github.com/meta-qt5/meta-qt5.git.
I built the meta-toolchain-qt5 and got the same error (see attached).
I'm using Ubuntu 12.04. Should I upgrade to 14.04?
Hello!
I think i've the same or problem.
i'm using ubuntu 14.04. and try to bitbake the "meta-toolchain" for nitrogen6x.
The configure of the alsa lib fails: "nativesdk-alsa-lib-1.0.27.2-r0 do_configure"
I've attached the logfile!
Error:
checking for x86_64-pokysdk-linux-gcc... x86_64-pokysdk-linux-gcc --sysroot=/iosono/imx6/yocto/master-next/build/tmp/sysroots/cortexa9hf-vfp-neon-mx6-pokysdk-linux
checking whether the C compiler works... no
Maybe the problem is related to the given sysroot path - because the given path doesn't exist on my machine
- maybe this is the problem?
I appreciate every hint you might have.
regards,
Lutz Altmann