Bug 4422

Summary: Poky build thyself
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: tf <tf+bugs.yocto>
Component: meta-yoctoAssignee: Cristian Iorga <cristian.iorga>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, sgw
Version: unspecified   
Target Milestone: 1.5   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
atom-pc core-image-minimal BA build
none
atom-pc core-image-minimal BA build dylan release 9.0.0 none

Description tf 2013-04-25 18:05:53 UTC 
I am trying build a Yocto image that would allow me to build Yocto images, along the lines of the build appliance, but an actual installable system rather than a VM image. I have run into a couple of issues that Ross asked me to document here for future rerence.

The build image recipe is based on the build appliance image recipe, minus the graphics components (I am running on a headless build machine, and I am only building images that themselves are headless); the images I am trying to build are slightly customized version core-image-minimal.

It fails very early on in the build:

libunistring-native: this uses iconv and has an awesome test for 'working iconv': some clever spark thought that a good way to test if iconv is working is to translate strings into a bunch of Japanese locales, so on a minimal Yocto system the lib gets built without iconv support, which then makes guile-native to fail. I think best fix would be to hang the author of that clever test by their ears and let them reflect on the wisdom of their ways. Other than that, adding am_cv_func_iconv_works=yes to EXTRA_OECONF works, though is not nice.

guile-native: once libunistring-native is built with iconv support, this at least configures, only to promptly fail to build; the first problem is that it is trying to build some documentation in that modern and most widely used info format; this can be patched out. Alas, it then fails to build anyway -- from a cursory examination the uinstalled guild script needs some of the modules it's trying to build, i.e., I suspect it's not possible to create guile ex nihili, but I could be wrong about that.

I gather it's grub that is pulling guile in in the first place, so perhaps the real fix is to get rid of grub?

I am wondering if someone could confirm whether it is possible to build core-image-minimal using the build appliance image from current master?
Comment 1 tf 2013-04-29 20:20:04 UTC 
I run into another issue: it would appear that the target gcc Yocto builds does not support SSP which is needed to build sudo (the sudo recipe has a compile_preppend fragment to build a couple of its native tools with the BUILD_CC, rather than having to build sudo-native, which then fails with libtool missing -lssp and -lssp_normal) I posted a patch to the list to fix the sudo breakage, though I suspect the sudo breakage is a symptom of some other issue.

I also looked into using syslinux instead of grub for the non-effi installs, and this happens to be a fairly trivial change to the install.sh scritp. I gather recent syslinux also supports effi, so perhaps ditching grub completely is entierly viable option.
Comment 2 Saul Wold 2013-04-29 22:32:23 UTC 
I just completed a build with the VMware Player and Build-Appliance image from master. I have in the past built and booted the build appliance in qemu and hardware, so I know it's doable.
Comment 3 tf 2013-04-30 10:00:12 UTC 
(In reply to comment #2)
> I just completed a build with the VMware Player and Build-Appliance image
> from master. I have in the past built and booted the build appliance in qemu
> and hardware, so I know it's doable.

I think lot depends on the target machine, I don't think Qemu images pull in grub?
Also good test is to build the appliance image using an appliance image.
Comment 4 Cristian Iorga 2013-07-03 11:23:45 UTC 
Hello tf,

Can you please provide a clear test-case for this bug, with all the needed steps?

Thanks,
Cristian
Comment 5 tf 2013-07-03 11:34:41 UTC 
(In reply to comment #4)
> Can you please provide a clear test-case for this bug, with all the needed
> steps?

There are no special steps needed, just try to build an image that includes grub for a real x86 machine using the build appliance; building core-image-minimal for something like atomp-pc or the nuc (meta-intel) should be enough.
Comment 6 Cristian Iorga 2013-07-03 11:39:51 UTC 
Hello,

Can you please provide the poky version used for testing? (HEAD commit).

Tests following your scenario were performed by me in the past, and were completed without problems.

That's why I am asking for the specific poky version.

Regards,
Cristian
Comment 7 tf 2013-07-03 12:05:32 UTC 
(In reply to comment #6)
> Can you please provide the poky version used for testing? (HEAD commit).

That would be the orignal dylan release, i.e., dylan-9.0.0 tag.
Comment 8 Cristian Iorga 2013-07-03 14:06:29 UTC 
Created attachment 1300 [details]
atom-pc core-image-minimal BA build

Hello,

During my tests atom-pc core-image-minimal builds OK under BA built from master.

I will also perform this test on dylan YP release.

Regards,
Cristian
Comment 9 Cristian Iorga 2013-07-04 11:11:34 UTC 
Created attachment 1301 [details]
atom-pc core-image-minimal BA build dylan release 9.0.0

Hello,

Tested again on dylan 9.0.0 BA downloadable image from yoctoproject.org.
During my tests atom-pc core-image-minimal builds OK under BA dylan release.

Regards,
Cristian
Comment 10 Cristian Iorga 2013-07-04 11:15:35 UTC 
No able to reproduce it using the test case provided by reporter.