Hi Xavier,
*From:*Xavier Roche [mailto:[email protected]]
*Sent:* Wednesday, January 21, 2015 2:44 PM
*To:* VanCutsem, Geoffroy
*Cc:* Kévin THIERRY; Wu, DaweiX; Saul Wold; [email protected]
*Subject:* Re: [Dev] Yocto build linux-yocto fail for Tizen IVI
Modello dev 32bit image
Hi Geoffroy,
I have reproduced the exact same issue has you described.
Basically, you can find the defconfig files in
meta-tizen/meta-tizen-adaptation/meta/recipes-kernel/linux/linux-yocto/ .
Thanks, I did a quick experiment yesterday and deleted the defconfig
found under x86_64 but that did not help… that makes me think that it
wasn’t that one the culprit and there is something else changing the
kernel config. Do you know how that defconfig file relates to the
{i386|x86_64}_defconfig files found in the kernel sources (under
arch/x86/configs/)?
During the do_kernel_configme step, the passed defconfig file seems
not to be taken into account, and as a result, it generates an other
one which enables some x86_64 based configs. (as you have already
noticed in the .config file).
I'm currently working on that issue, but in the mid time here is a
dirty work around that could help you to generate an image :
1. Once linux-yocto has crashed, tape the following : bitbake
linux-yocto -c menuconfig
2. Disable the 64-bit kernel option (must be the first option), Esc
and save the conf (enter)
3. relaunch the kernel build : bitbake -kv linux-yocto
Hope this could help!
That workaround did the trick, thanks!
Regards,
Xavier
--
Xavier Roche
Intel OTC
On 21/01/2015 11:26, VanCutsem, Geoffroy wrote:
Excuse the newbie question but where exactly can I find these defconfig
files? I thought they were part of the kernel sources but you seem to indicate
they are actually somewhere in meta-tizen but I couldn't find them there?
I noticed the following messages in log.do_kernel_configcheck:
<snip>
[required redefined (2)]:
.meta/cfg/standard/genericx86/required_redefinition.txt
required kernel config options were redefined (and changed)
during processing this BSP. This means that required values are
are changed from their initial value.
DEBUG: Python function do_kernel_configcheck finished
</snip>
What does that mean and what triggers this?
Here is some additional info that may be useful to the experts out there.
log.do_kernel_configme file:
[gvancuts@localhost temp]$ less log.do_kernel_configme
DEBUG: Executing shell function do_kernel_configme
NOTE: kernel configme
[INFO] Configuring target/machine combo: "standard/genericx86"
[INFO] collecting configs in .meta/meta-series
[INFO] Pre-processed cfg file genericx86-standard-config-3.14.19 created.
[INFO] processing of raw cfg data completed.
********************************************************************************
Configuration stored in
/home/gvancuts/tizen-distro/build-ivi-x86/tmp-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a942_902f34d361-r0/linux-genericx86-standard-build/.config
********************************************************************************
To build with this kernel configuration, ensure a suitable toolchain
is in your path for x86, note its common command prefix, and do:
make
O=/home/gvancuts/tizen-distro/build-ivi-x86/tmp-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a942_902f34d361-r0/linux-genericx86-standard-build
ARCH=x86 \
CROSS_COMPILE=<cross-compile-prefix>
DEBUG: Shell function do_kernel_configme finished
The .config file generated (and used) starts with the following
(suspicious) lines:
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.14.19 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
Thanks,
Geoffroy
-----Original Message-----
From: Dev [mailto:[email protected]] On Behalf Of Kévin
THIERRY
Sent: Wednesday, January 21, 2015 9:38 AM
To: Wu, DaweiX; Saul Wold;[email protected]
<mailto:[email protected]>
Subject: Re: [Dev] Yocto build linux-yocto fail for Tizen IVI Modello
dev 32bit
image
Hi,
We already encountered that issue which was due to a wrong defconfig
being used (x86_64 instead of i586 or the opposite). I suspect this is
also the case with your current issue. You can easily check that by
deleting all but the correct defconfig in meta-tizen, cleaning the
kernel build and try it again. If it succeeds it means the wrong
defconfig is being used and we will have to investigate why.
Kevin
On 01/21/2015 06:12 AM, Wu, DaweiX wrote:
Only edit MACHINE to genericx86 . Here is the config. Steps: 1. cd
tizen-
distro 2. source tizen-ivi-init-build-env build32ivimodellodev 3.
bitbake tizen-ivi-
Modello-image-dev . It's clean build and I tired ' bitbake linux-yocto
-c cleanall '
,no helps.
Build Configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "i586-oe-linux"
MACHINE = "genericx86"
DISTRO = "tizen-ivi"
DISTRO_VERSION = "3.0"
TUNE_FEATURES = "m32 core2"
TARGET_FPU = ""
meta
meta-oe
meta-multimedia
meta-ruby
meta-systemd
meta-gnome
meta
meta-oe
meta-tizen-common-base
meta-tizen-common-share
meta-tizen-common-devtools
meta-tizen-common-demo
meta-tizen-ivi = "tizen:4d13fc323cb96e3ba36d7acdb6f8ab034add91d0"
-----Original Message-----
From: Saul Wold [mailto:[email protected]]
Sent: Wednesday, January 21, 2015 11:06 AM
To: Wu, DaweiX;[email protected] <mailto:[email protected]>
Subject: Re: [Dev] Yocto build linux-yocto fail for Tizen IVI
Modello dev 32bit
image
On 01/20/2015 06:37 PM, Wu, DaweiX wrote:
Hi All, I tried to build Tizen IVI Modello 32bit image ,but
failed at linux-
yocto. Here are my env and build errors.
Host: 64bit Ubuntu14.04 16GRAM
Tizen-distro version: 4d13fc323cb96e3ba36d7acdb6f8ab034add91d0
Can you provide more information, just as the contents of your
local.conf file
in the build area, also what steps you did leading up to tihs? Was it
from an
existing build or a clean build?
Thanks
Sau!
Build error:
/home/test/tizen-Distro-latest/tizen-distro.1/build32ivimodellodev/tmp
-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a
942_902f34d361-r0/linux/scripts/mod/empty.c:1:0: error: code
model
'kernel' not supported in the 32 bit mode
| /* empty file to figure out endianness / word size */ ^
|
/home/test/tizen-Distro-latest/tizen-distro.1/build32ivimodellodev/t
|
mp-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6
| 271a942_902f34d361-r0/linux/scripts/mod/empty.c:1:0: sorry,
| unimplemented: 64-bit mode not compiled in
|
/home/test/tizen-Distro-latest/tizen-distro.1/build32ivimodellodev/t
|
mp-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6
| 271a942_902f34d361-r0/linux/scripts/Makefile.build:308:
recipe for
| target 'scripts/mod/empty.o' failed
| make[4]: *** [scripts/mod/empty.o] Error 1
|
/home/test/tizen-Distro-latest/tizen-distro.1/build32ivimodellodev/t
|
mp-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6
| 271a942_902f34d361-r0/linux/scripts/Makefile.build:455:
recipe for
| target 'scripts/mod' failed
| make[3]: *** [scripts/mod] Error 2
| make[3]: *** Waiting for unfinished jobs....
|
/home/test/tizen-Distro-latest/tizen-distro.1/build32ivimodellodev/t
|
mp-glibc/work/genericx86-oe-linux/linux-yocto/3.14.19+gitAUTOINC+fb6
| 271a942_902f34d361-r0/linux/Makefile:527: recipe for target
| 'scripts' failed
Thanks,
Dawei
_______________________________________________
Dev mailing list
[email protected] <mailto:[email protected]>
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected] <mailto:[email protected]>
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected] <mailto:[email protected]>
https://lists.tizen.org/listinfo/dev
-----------------------------------------------
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718.
Citibank, Brussels, account 570/1031255/09
_______________________________________________
Dev mailing list
[email protected] <mailto:[email protected]>
https://lists.tizen.org/listinfo/dev
-----------------------------------------------
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718.
Citibank, Brussels, account 570/1031255/09
