I changed a bit trying to fix this.
- I have gone from dylan-9.0.2 to dylan-9.0.4
- I had to downgrade git from 1.9.1 to 1.8.5 to fix another error.
Still get the same kernel_configme error.
A bunch of logs around the build time are attached in this zip file
Not sure about the kernel config error, theh only thing that comes to my mind is - try running config process manually by running "bitbake -c devshell linux-yocto-clanton", this will drop you in a shell with prepared environment where you can then run "make oldconfig" and other standard kernel config/compile commands. Maybe you'll be able to extract some more information that way.
There are also a bnuch of warnings like this:
NOTE: consider defining a PREFERRED_PROVIDER entry to match glibc-gconv-ibm850-native
NOTE: multiple providers are available for runtime glibc-gconv-ibm437-native (eglibc-locale, nativesdk-eglibc-locale)
The number after ibm varies. How can I fix this?
are harmless, if that's what you mean, so you can simply ignore them. If your goal is namely to get rid of them - then I've no idea, sorry, haven't pursued that, just always ignored
I meeting the same problems with xx. And I don't now how to solve it. Can you help me? Thanks a lot!
After a few days struggle, I finally finished downloading the packages which yocto need for Galileo. But now I meets this do_kernel_configme error problem.
The content of log.do_kernel_configme.5623 is:
DEBUG: Executing shell function do_kernel_configme
[INFO] doing kernel configme
[INFO] Configuring target/machine combo: "standard/clanton"
[INFO] collecting configs in ./meta/meta-series
mv: target `3.8.7' is not a directory
creation of pre-processed config data failed
config of "standard/clanton" failed
ERROR: Function failed: do_kernel_configme (see /home/johnny/Galileo/Board_Support_Package_Sources_for_Intel_Quark_v1.0.0/meta-clanton_v1.0.0/yocto_build/tmp/work/clanton-poky-linux-uclibc/linux-yocto-clanton/3.8-r0/temp/log.do_kernel_configme.5623 for further information)
And I use CentOS running in vmware workstation.
Waiting for your help, many thanks!
what for do you need the image?
Maybe meta-intel-iot-devkit - Intel IoT Developer Kit metadata is of interest for you as well? The devkit-daisy-multilibc branch is eglibc with included uclibc libs to allow to run sketches directly from Arduino IDE. Maybe this builds better for you?
I just built the firmware following section 4 in the Intel® Quark™ BSP Build and Software User Guide without any issues. Can you please provide parameters you passed when executing buildallconfigs.sh? or any additional modifications?
Mine was :
./buildallconfigs.sh GCC46 QuarkPlatform #Based on GCC46
Looks like i misunderstood your question. I am currently building image-full-galileo. so far no errors. Did you customized anything? I am building following the commands in the BSP documents.
I build the image following section 6 of the BSP Document. I am running Debian 64 Bit. These are the commands i used:
7z x Board_Support_Package_Sources_for_Intel_Quark_v22.214.171.124z tar -xvf meta-clanton_v1.0.0.tar.gz cd meta-clanton_v1.0.0/ ./setup.sh source poky/oe-init-build-env yocto_build/ bitbake image-full-galileo
I did not get any errors. Are you modifying any files before building?
Thank you Jesus! I built image-spi successfully in Debian 7.5 according to your advice!
But still there are two questions confused me.
(1) I suppose Board_Support_Package_Sources_for_Intel_Quark_v1.0.0_full_yocto_archive.tar.bz2 is the MIRRORS of the source for building, am I right?
(2) To speed up the building process, I don't want yocto to fetch sources from internet, I want yocto do fetch from Board_Support_Package_Sources_for_Intel_Quark_v1.0.0_full_yocto_archive.tar.bz2. I exact it and put them in /home/johnny/Galileo/full (I put those files together in one directory). And I added some sentences in yocto_build/conf/local.conf:
SOURCE_MIRROR_URL ?= "file:///home/johnny/Galileo/full"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
but it seems doesn't work, I saw yocto still fetch from internet, why?
Thank you! :-)