All of lore.kernel.org
 help / color / mirror / Atom feed
* some issues with current poky master
@ 2017-08-17  8:00 Markus Volk
  2017-08-17 23:34 ` Markus Volk
  2017-08-21 11:24 ` Markus Volk
  0 siblings, 2 replies; 5+ messages in thread
From: Markus Volk @ 2017-08-17  8:00 UTC (permalink / raw)
  To: yocto


Hello,

yesterday i tried building an image using the current poky master branch. I had some issues, not sure which of them are homemade but i´d like to share anyway


for mesa package_qa fails with:

ERROR: mesa-2_17.1.5-r0 do_package_qa: QA Issue: package libxatracker contains bad RPATH /home/builder/yocto/poky/build/tmp/work/x86_64-linux/llvm-native/5.0-r0/recipe-sysroot-native/usr/lib:/home/builder/yocto/poky/build/tmp/work/x86_64-linux/llvm-native/5.0-r0/recipe-sysroot-native/lib in file /home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/mesa/2_17.1.5-r0/packages-split/libxatracker/usr/lib/libxatracker.so.2.3.0 [rpaths]
ERROR: mesa-2_17.1.5-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: mesa-2_17.1.5-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/mesa/2_17.1.5-r0/temp/log.do_package_qa.12561
ERROR: Task (/home/builder/yocto/poky/meta/recipes-graphics/mesa/mesa_17.1.5.bb:do_package_qa) failed with exit code '1'
NOTE: Tasks Summary: Attempted 8980 tasks of which 8970 didn't need to be rerun and 1 failed.

i added 'INSANE_SKIP_libxatracker = "rpaths"  into a bbappend to go on

further, i´m packaging chrome. I encounter problems here since pyro with unpacking the .deb 

When doing 'bitbake myimage' it stoppes here:

ERROR: chrome-browser-r0 do_unpack: Unpack failure for URL: 'https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb'. Unpack command PATH="/home/builder/yocto/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/builder/yocto/poky/scripts:/home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/recipe-sysroot/usr/bin/crossscripts:/home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/recipe-sysroot-native/usr/sbin:/home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/recipe-sysroot-native/usr/bin:/home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/recipe-sysroot-native/sbin:/home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/recipe-sysroot-native/bin:/home/builder/yocto/poky/bitbake/bin:/home/builder/yocto/poky/build/tmp/hosttools" ar x /home/builder/yocto/poky/yocto-downloads/google-chrome-stable_current_amd64.deb data.tar.xz && tar --no-same-owner -xpf data.tar.xz && rm data.tar.xz failed with return value 2
ERROR: chrome-browser-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: /home/builder/yocto/poky/build/tmp/work/core2-64-poky-linux/chrome/browser-r0/temp/log.do_unpack.16529
ERROR: Task (/home/builder/yocto/poky/meta-neutrino-x86/recipes-local/chrome/chrome_browser.bb:do_unpack) failed with exit code '1'

after doing

'bitbake -c cleansstate chrome'
'bitbake chrome'

it is working then, unless the .deb is removed from download directory. Maybe i´m missing something inside the .bb ?

SUMMARY = "Google Chrome"
LICENSE = "proprietary"
LIC_FILES_CHKSUM = "file://${WORKDIR}/license;md5=17a6b3d5436a55985b200c725761907a"

SRC_URI = "https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb \
	   file://license \
"

SRC_URI[md5sum] = "70f90d19dcf51a87b7f6df788b5fddc7"
SRC_URI[sha256sum] = "5c22cc312c360cf7ad84f5f75c6fc6626b59ca529f7f66f65aaab3b9ca8df196"


DEPENDS = "xz-native"
RDEPENDS_${PN} += "cups"

S = "${WORKDIR}"

do_install() {
	install -d ${D}/usr/bin ${D}/usr/share/applications ${D}/opt/google
	cp -rf ${S}/opt/* ${D}/opt/
	cp -rf ${S}/usr/* ${D}/usr/
	ln -sf ./google-chrome-stable ${D}/usr/bin/google-chrome
	cp -rf ${S}/etc/* ${D}${sysconfdir}
	for i in 16 32 48 128 256;do
		x='x'
		install -d ${D}/usr/share/icons/hicolor/$i$x$i/apps
		cp -f ${S}/opt/google/chrome/product_logo_$i.png ${D}/usr/share/icons/hicolor/$i$x$i/apps/google-chrome.png
	done
}

FILES_${PN} = "/usr \
		       /opt \
		       /etc \
"

INSANE_SKIP_${PN} += "already-stripped ldflags build-deps file-rdeps"

After sucessful build of the Image, my .iso has 38MB in size and seems to be missing the entire rootfs
The created hddimg has the right size of 4,3GB, but when i write it onto an usb drive (tried dd and gnome-disk-utility) it ends up with a big /boot partiton containing only the boot files

regards,
Markus
-- 
Markus Volk <f_l_k@t-online.de>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: some issues with current poky master
  2017-08-17  8:00 some issues with current poky master Markus Volk
@ 2017-08-17 23:34 ` Markus Volk
  2017-08-18 14:03   ` Leonardo Sandoval
  2017-08-21 11:24 ` Markus Volk
  1 sibling, 1 reply; 5+ messages in thread
From: Markus Volk @ 2017-08-17 23:34 UTC (permalink / raw)
  To: yocto


 
> After sucessful build of the Image, my .iso has 38MB in size and seems to be missing the entire rootfs
> The created hddimg has the right size of 4,3GB, but when i write it onto an usb drive (tried dd and gnome-disk-utility) it ends up with a big /boot partiton containing only the boot files
> 

I still do not know if this is a homemade one, but i saw inside the do_bootimg log that isolevel 3 was missing for mkisofs because the rootfs is too big without.

For me this here inside image-live.bbclass fails for some reason:

	# Check the size of ${ISODIR}/rootfs.img, use mkisofs -iso-level 3
	# when it exceeds 3.8GB, the specification is 4G - 1 bytes, we need
	# leave a few space for other files.
	mkisofs_iso_level=""

        if [ -n "${ROOTFS}" ] && [ -s "${ROOTFS}" ]; then
		rootfs_img_size=`stat -c '%s' ${ISODIR}/rootfs.img`
		# 4080218931 = 3.8 * 1024 * 1024 * 1024
		if [ $rootfs_img_size -gt 4080218931 ]; then
			bbnote "${ISODIR}/rootfs.img execeeds 3.8GB, using '-iso-level 3' for mkisofs"
			mkisofs_iso_level="-iso-level 3"
		fi
	fi



hard coding mkisofs_iso_level to

	mkisofs_iso_level="-iso-level 3"

fixes this up
-- 
Markus Volk <f_l_k@t-online.de>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: some issues with current poky master
  2017-08-17 23:34 ` Markus Volk
@ 2017-08-18 14:03   ` Leonardo Sandoval
  2017-08-19 18:36     ` Markus Volk
  0 siblings, 1 reply; 5+ messages in thread
From: Leonardo Sandoval @ 2017-08-18 14:03 UTC (permalink / raw)
  To: Markus Volk; +Cc: yocto

On Fri, 2017-08-18 at 01:34 +0200, Markus Volk wrote:
>  
> > After sucessful build of the Image, my .iso has 38MB in size and seems to be missing the entire rootfs
> > The created hddimg has the right size of 4,3GB, but when i write it onto an usb drive (tried dd and gnome-disk-utility) it ends up with a big /boot partiton containing only the boot files
> > 
> 
> I still do not know if this is a homemade one, but i saw inside the do_bootimg log that isolevel 3 was missing for mkisofs because the rootfs is too big without.
> 
> For me this here inside image-live.bbclass fails for some reason:
> 
> 	# Check the size of ${ISODIR}/rootfs.img, use mkisofs -iso-level 3
> 	# when it exceeds 3.8GB, the specification is 4G - 1 bytes, we need
> 	# leave a few space for other files.
> 	mkisofs_iso_level=""
> 
>         if [ -n "${ROOTFS}" ] && [ -s "${ROOTFS}" ]; then
> 		rootfs_img_size=`stat -c '%s' ${ISODIR}/rootfs.img`
> 		# 4080218931 = 3.8 * 1024 * 1024 * 1024
> 		if [ $rootfs_img_size -gt 4080218931 ]; then
> 			bbnote "${ISODIR}/rootfs.img execeeds 3.8GB, using '-iso-level 3' for mkisofs"
> 			mkisofs_iso_level="-iso-level 3"
> 		fi
> 	fi
> 

not really sure what you have changed in the code (better to send a diff
snippet), so proposed your change to the oe-core.

> 
> 
> hard coding mkisofs_iso_level to
> 
> 	mkisofs_iso_level="-iso-level 3"
> 
> fixes this up
> -- 
> Markus Volk <f_l_k@t-online.de>




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: some issues with current poky master
  2017-08-18 14:03   ` Leonardo Sandoval
@ 2017-08-19 18:36     ` Markus Volk
  0 siblings, 0 replies; 5+ messages in thread
From: Markus Volk @ 2017-08-19 18:36 UTC (permalink / raw)
  To: Leonardo Sandoval; +Cc: yocto

The problem here is, that 'stat -c %s' gives out a wrong value. The issue happens only, if /bin/stat is linked to /bin/stat.stat. If using /bin/stat.coreutils the filesize is displayed correctly


-- 
Markus Volk <f_l_k@t-online.de>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: some issues with current poky master
  2017-08-17  8:00 some issues with current poky master Markus Volk
  2017-08-17 23:34 ` Markus Volk
@ 2017-08-21 11:24 ` Markus Volk
  1 sibling, 0 replies; 5+ messages in thread
From: Markus Volk @ 2017-08-21 11:24 UTC (permalink / raw)
  To: yocto


> it is working then, unless the .deb is removed from download directory. Maybe i´m missing something inside the .bb ?
> 

Unpacking .deb packages can be done by including

do_unpack[depends] += "xz-native:do_populate_sysroot \ 
		       tar-native:do_populate_sysroot \
		       binutils-native:do_populate_sysroot \
"

I don´t know for sure if all of those are needed, but i wanted to be safe

-- 
Markus Volk <f_l_k@t-online.de>


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2017-08-21 11:24 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-17  8:00 some issues with current poky master Markus Volk
2017-08-17 23:34 ` Markus Volk
2017-08-18 14:03   ` Leonardo Sandoval
2017-08-19 18:36     ` Markus Volk
2017-08-21 11:24 ` Markus Volk

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.