Re: [yocto] Problem compiling diffutils on poky-tiny in danny
Hi Tim, On 14/11/12 01:11, Tim Bird wrote: > ./wctype.h:448:1: error: static declaration of 'iswalnum' follows non-static > declaration > ./wctype.h:460:1: error: static declaration of 'iswalpha' follows non-static > declaration > ... > Has anyone seen this type of error before, or can provide some > hints of what to check or adjust to fix this? The diffutils package provides a replacement for wctypes.h, which includes the system wctypes.h and then adds some stuff of it's own -- I think you are hitting the '#if !GNULIB_defined_wctype_functions' in the replacement file, which expects to be providing iswalnum, etc., and prototypes them as 'static inline'; the system wctypes.h protypes are not static. Not sure why it should be taking that path, could be because these functions are not provided by libc for poky-tiny (in which case the libc headers need patching), or could be the detection in diffutils is broken. As a quick hack, try removing the offending prototypes from the sysroot wctypes.h. Tomas -- http://sleepfive.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] No package is created after do_install
Am 12.11.2012 14:44, schrieb Peter Oruba:
Hello everybody
I am using Yocto as a framework to build Debian packages. So far there
is a recipe working up to the stage that source is fetched and copied
(for now compiling is simply skipped). That part works fine, however, I
am having a hard time to create a Debian package with ${destdir}'s content.
The recipe looks as follows:
LICENSE = "MyLicense"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c6564c1e3c8492bdfa4eddb6d81c2c66"
#SRCDATE
SRCREV="r105"
PV="${SRCPV}"
PR="${SRCREV}"
SRC_URI = "svn://repo/trunk;module=myproject;proto=http"
S = "${WORKDIR}/${PN}"
PKG="myproject-debian"
PKGFN="myproject"
IMAGE_ROOTFS="${D}"
PN="myproject"
PACKAGE_ARCH = "${MACHINE_ARCH}"
PACKAGES = "${PN}"
FILES_${PN} = "${D}/usr/libexec/*"
inherit native package_deb
do_install() {
#oe_runmake 'DESTDIR=${D}' install
install -v -d ${D}/usr/libexec/
cp -a -v ${S} ${D}/usr/libexec/
}
do_populate_sysroot[noexec] = "1"
do_package[noexec] = "0"
do_package_write[noexec] = "0"
do_package_write_deb[noexec] = "0"
Unfortunately there is not a lot of information about creating native
packages with Yocto that you can find out there.
Thanks,
Peter
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Managed to make it work, problem was solved by removing the following lines:
do_package[noexec] = "0"
do_package_write[noexec] = "0"
do_package_write_deb[noexec] = "0"
Thanks,
Peter
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-ivi][PATCH 1/2] dlt-daemon: Package utils, libraries, test etc. separately
Signed-off-by: Andrei Gherzan
---
recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb | 24 +++---
1 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
b/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
index 9cdbfc0..7a20647 100644
--- a/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
+++ b/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
@@ -11,7 +11,7 @@ DESCRIPTION = "This component provides a standardised log and
trace interface, b
HOMEPAGE = "https://www.genivi.org/";
SECTION = "console/utils"
-PR = "r0"
+PR = "r1"
inherit gzipnative
@@ -25,9 +25,25 @@ S = "${WORKDIR}/git"
inherit autotools gettext cmake
-FILES_${PN}-doc += "/usr/share/*"
+PACKAGES =+ "${PN}-systemd \
+ libdlt \
+ dlt-adaptor \
+ dlt-convert \
+ dlt-example \
+ dlt-receive \
+ dlt-system \
+ dlt-test \
+ "
+
+FILES_libdlt = "${libdir}/*${SOLIBS}"
+FILES_dlt-adaptor = "${bindir}/dlt-adaptor*"
+FILES_dlt-convert = "${bindir}/dlt-convert*"
+FILES_dlt-example = "${bindir}/dlt-example*"
+FILES_dlt-receive = "${bindir}/dlt-receive*"
+FILES_dlt-system = "${bindir}/dlt-system* \
+ ${sysconfdir}/dlt-system.conf"
+FILES_dlt-test = "${bindir}/dlt-test* \
+ ${datadir}/dlt-filetransfer"
FILES_${PN}-systemd += "${systemd_unitdir}/system/"
-PACKAGES =+ "${PN}-systemd"
-
EXTRA_OECMAKE = "-DWITH_SYSTEMD=ON"
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-ivi][PATCH 2/2] dlt-daemon: Use systemd class from meta-systemd
Signed-off-by: Andrei Gherzan
---
recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb | 31 ++
1 files changed, 25 insertions(+), 6 deletions(-)
diff --git a/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
b/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
index 7a20647..52a69f8 100644
--- a/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
+++ b/recipes-extended/dlt-daemon/dlt-daemon_2.9.0.bb
@@ -11,7 +11,7 @@ DESCRIPTION = "This component provides a standardised log and
trace interface, b
HOMEPAGE = "https://www.genivi.org/";
SECTION = "console/utils"
-PR = "r1"
+PR = "r2"
inherit gzipnative
@@ -23,11 +23,30 @@ SRC_URI =
"git://git.projects.genivi.org/${PN}.git;protocol=git;tag=v${PV}"
S = "${WORKDIR}/git"
-inherit autotools gettext cmake
+inherit autotools gettext cmake systemd
-PACKAGES =+ "${PN}-systemd \
+SYSTEMD_PACKAGES = " \
+dlt-adaptor-udp-systemd \
+dlt-receive-systemd \
+dlt-system-systemd \
+dlt-example-systemd \
+dlt-daemon-systemd \
+"
+SYSTEMD_SERVICE_dlt-adaptor-udp-systemd = "dlt-adaptor-udp.service"
+SYSTEMD_AUTO_ENABLE_dlt-adaptor-udp-systemd = "disable"
+SYSTEMD_SERVICE_dlt-receive-systemd = "dlt-receive.service"
+SYSTEMD_AUTO_ENABLE_dlt-receive-systemd = "disable"
+SYSTEMD_SERVICE_dlt-system-systemd = "dlt-system.service"
+SYSTEMD_AUTO_ENABLE_dlt-system-systemd = "disable"
+SYSTEMD_SERVICE_dlt-example-systemd = "dlt-example-user.service"
+SYSTEMD_AUTO_ENABLE_dlt-example-systemd = "disable"
+SYSTEMD_SERVICE_${PN}-systemd = "dlt.service"
+SYSTEMD_AUTO_ENABLE_${PN}-systemd = "disable"
+
+PACKAGES =+ " \
libdlt \
- dlt-adaptor \
+ dlt-adaptor-udp \
+ dlt-adaptor-stdin \
dlt-convert \
dlt-example \
dlt-receive \
@@ -36,7 +55,8 @@ PACKAGES =+ "${PN}-systemd \
"
FILES_libdlt = "${libdir}/*${SOLIBS}"
-FILES_dlt-adaptor = "${bindir}/dlt-adaptor*"
+FILES_dlt-adaptor-udp = "${bindir}/dlt-adaptor-stdin"
+FILES_dlt-adaptor-stdin = "${bindir}/dlt-adaptor-udp"
FILES_dlt-convert = "${bindir}/dlt-convert*"
FILES_dlt-example = "${bindir}/dlt-example*"
FILES_dlt-receive = "${bindir}/dlt-receive*"
@@ -44,6 +64,5 @@ FILES_dlt-system = "${bindir}/dlt-system* \
${sysconfdir}/dlt-system.conf"
FILES_dlt-test = "${bindir}/dlt-test* \
${datadir}/dlt-filetransfer"
-FILES_${PN}-systemd += "${systemd_unitdir}/system/"
EXTRA_OECMAKE = "-DWITH_SYSTEMD=ON"
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/13/2012 05:11 PM, Tim Bird wrote: > Hi all, > > I'm using DISTRO=poky-tiny and trying to build: > $ bitbake core-image-minimal-initramfs > > I get the following error trying to compile diffutils: > > ... > i586-poky-linux-gcc -m32 -march=i586 > --sysroot=/a/home/tbird/work/yocto/danny-test1/tmp/sysroots/qemux86 > -std=gnu99 -I. -O2 -pipe -g -feliminate-unused-debug-types -c -o > wcwidth.o wcwidth.c > In file included from wcwidth.c:23:0: > ./wctype.h:448:1: error: static declaration of 'iswalnum' follows non-static > declaration > ./wctype.h:460:1: error: static declaration of 'iswalpha' follows non-static > declaration > ... Is there an option to build diffutils without wide character support? This is something tiny does away with and frequent point of failure when trying to build additional packages with it. > See the attached compile log for details. > > Has anyone done this recently? Is this one of the supported images for > this distro (poky-tiny)? I don't build that target as I use the cpio.gz from core-image-minimal as an initial ramdisk. Is there a particular reason you want to build "core-image-minimal-initramfs" specifically? > > Has anyone seen this type of error before, or can provide some > hints of what to check or adjust to fix this? Yup, it's wide characters being required by diffutils and being excluded by the poky-tiny DISTRO_FEATURES_LIBC assignment. If supported by diffutils, we might be able to test ENABLE_WIDEC in diffutils and configure accordingly (see the ncurses recipes for an example). Thanks, -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-freescale general mailing list
YoctoProject.org is now hosting a meta-freescale mailing list that are going to unify the communities of meta-fsl-ppc and meta-fsl-arm. >From now on all patches affecting meta-fsl-ppc and meta-fsl-arm can be sent to meta-freesc...@yoctoproject.org and have the respective tag in the patch. Please check the README in respective layer about the command line to use for git format-patch. Please subscribe here: https://lists.yoctoproject.org/listinfo/meta-freescale Archives here: https://lists.yoctoproject.org/pipermail/meta-freescale/ -Matthew ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 08:48 AM, Darren Hart wrote: > > > On 11/13/2012 05:11 PM, Tim Bird wrote: >> Hi all, >> >> I'm using DISTRO=poky-tiny and trying to build: >> $ bitbake core-image-minimal-initramfs >> >> I get the following error trying to compile diffutils: >> >> ... >> i586-poky-linux-gcc -m32 -march=i586 >> --sysroot=/a/home/tbird/work/yocto/danny-test1/tmp/sysroots/qemux86 >> -std=gnu99 -I. -O2 -pipe -g -feliminate-unused-debug-types -c -o >> wcwidth.o wcwidth.c >> In file included from wcwidth.c:23:0: >> ./wctype.h:448:1: error: static declaration of 'iswalnum' follows non-static >> declaration >> ./wctype.h:460:1: error: static declaration of 'iswalpha' follows non-static >> declaration >> ... > > > Is there an option to build diffutils without wide character support? > This is something tiny does away with and frequent point of failure > when trying to build additional packages with it. I'll see if I can find something. > >> See the attached compile log for details. >> >> Has anyone done this recently? Is this one of the supported images for >> this distro (poky-tiny)? > > > I don't build that target as I use the cpio.gz from core-image-minimal > as an initial ramdisk. Is there a particular reason you want to build > "core-image-minimal-initramfs" specifically? Building poky-tiny with core-image-minimal worked fine. I didn't understand that this built multiple images (including a cpio.gz), and thought that the default method of building a cpio.gz was to build the -initramfs image. So, no, I don't have a particular reason to do this. Also, I'm not sure I am doing the startup initialization with runqemu correctly. I wouldn't have expected any rootfs to be used for this image, but the default invocation of runqemu uses one. An example shows use of a 'ramfs' parameter. I think I need to dig into runqemu and verify args are appropriate for an initramfs. > >> >> Has anyone seen this type of error before, or can provide some >> hints of what to check or adjust to fix this? > > Yup, it's wide characters being required by diffutils and being excluded > by the poky-tiny DISTRO_FEATURES_LIBC assignment. If supported by > diffutils, we might be able to test ENABLE_WIDEC in diffutils and > configure accordingly (see the ncurses recipes for an example). I'll poke around. I'm curious why poky-tiny core-image-minimal built OK, but core-image-minimal-initramfs didn't. I didn't expect any difference in target-side binaries between the two - only some changes in the image build steps. Thanks for the tips. I'll check it out. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] do_fetch failure with libowl-0.1
Looks like the downloaded source file is corrupted although that should be caught by the checksum verification. Try to locate the source file in DL_DIR and unpack it manually. If it is corrupt delete the file, run a cleanall on the libowl recipe and run bitbake again. Rudi On Nov 14, 2012 10:39 AM, "Ramming, Brian" wrote: > Hello, > > ** ** > > I am looking into converting my layer from Yocto 1.2 to Yocto 1.3 running > into an issue when trying to build my image. It fails when trying to fetch > libowl-0.1: > > ** ** > > ERROR: Fetcher failure: Fetch command failed with exit code 2, output: > > tar: Skipping to next header > > ** ** > > gzip: stdin: invalid compressed data--crc error > > ** ** > > gzip: stdin: invalid compressed data--length error > > tar: Child returned status 1 > > tar: Error is not recoverable: exiting now > > ** ** > > DEBUG: Python function base_do_fetch finished > > DEBUG: Python function do_fetch finished > > ERROR: Function failed: Fetcher failure for URL: 'git:// > git.yoctoproject.org/libowl;protocol=git'. Unable to fetch URL from any > source. > > ** ** > > ** ** > > I attached the full log from: > \build\tmp\work\core2-poky-linux\libowl-0.1+git1+6ebc8ac8f8575278dd40a535cadefa26374e44b1-r0 > > > ** ** > > If there is anything else that I should attach, or additional information > I should provide please let me know. > > ** ** > > Any information on this would be much appreciated. > > ** ** > > Thank you kindly, > > Brian R. > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 10:43 AM, Tim Bird wrote: > On 11/14/2012 08:48 AM, Darren Hart wrote: >> >> >> On 11/13/2012 05:11 PM, Tim Bird wrote: >>> Hi all, >>> >>> I'm using DISTRO=poky-tiny and trying to build: >>> $ bitbake core-image-minimal-initramfs >>> >>> I get the following error trying to compile diffutils: >>> >>> ... >>> i586-poky-linux-gcc -m32 -march=i586 >>> --sysroot=/a/home/tbird/work/yocto/danny-test1/tmp/sysroots/qemux86 >>> -std=gnu99 -I. -O2 -pipe -g -feliminate-unused-debug-types -c -o >>> wcwidth.o wcwidth.c >>> In file included from wcwidth.c:23:0: >>> ./wctype.h:448:1: error: static declaration of 'iswalnum' follows >>> non-static declaration >>> ./wctype.h:460:1: error: static declaration of 'iswalpha' follows >>> non-static declaration >>> ... >> >> >> Is there an option to build diffutils without wide character support? >> This is something tiny does away with and frequent point of failure >> when trying to build additional packages with it. > > I'll see if I can find something. > >> >>> See the attached compile log for details. >>> >>> Has anyone done this recently? Is this one of the supported images for >>> this distro (poky-tiny)? >> >> >> I don't build that target as I use the cpio.gz from core-image-minimal >> as an initial ramdisk. Is there a particular reason you want to build >> "core-image-minimal-initramfs" specifically? > > Building poky-tiny with core-image-minimal worked fine. I didn't understand > that this built multiple images (including a cpio.gz), and thought that > the default method of building a cpio.gz was to build the > -initramfs > image. So, no, I don't have a particular reason to do this. > > Also, I'm not sure I am doing the startup initialization with runqemu > correctly. I wouldn't have expected any rootfs to be used for this image, > but the default invocation of runqemu uses one. An example shows use of > a 'ramfs' parameter. I think I need to dig into runqemu and verify > args are appropriate for an initramfs. > runqemu doesn't quite know what to make of poky-tiny :-) Try the following: $ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz -nographic -append "console=ttyS0 root=/dev/ram0" I really need to get the poky-tiny docs going... right after I finish these kernel docs I guess... anyone want to volunteer? >> >>> >>> Has anyone seen this type of error before, or can provide some >>> hints of what to check or adjust to fix this? >> >> Yup, it's wide characters being required by diffutils and being excluded >> by the poky-tiny DISTRO_FEATURES_LIBC assignment. If supported by >> diffutils, we might be able to test ENABLE_WIDEC in diffutils and >> configure accordingly (see the ncurses recipes for an example). > > I'll poke around. I'm curious why poky-tiny core-image-minimal built > OK, but core-image-minimal-initramfs didn't. I didn't expect > any difference in target-side binaries between the two - only some > changes in the image build steps. > > Thanks for the tips. I'll check it out. Let me know what you find out. I thought the initramfs had the installer in it, but maybe that's included by some other mechanism. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 10:50 AM, Darren Hart wrote: > runqemu doesn't quite know what to make of poky-tiny :-) Try the following: > > $ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz > -nographic -append "console=ttyS0 root=/dev/ram0" Ahh. That's helpful. Thanks. > I really need to get the poky-tiny docs going... right after I finish > these kernel docs I guess... anyone want to volunteer? I'd be happy to write some stuff up. It wouldn't be exhaustive, but I could document what I've found out about (the LIBC_FEATURE stuff, and some of the dependencies I've found, as well as invocation tips and some of the differences between the poky default and poky-tiny packages and features). Where would you like it? Is there a wiki page or a doc already started? >>> Has anyone seen this type of error before, or can provide some hints of what to check or adjust to fix this? >>> >>> Yup, it's wide characters being required by diffutils and being excluded >>> by the poky-tiny DISTRO_FEATURES_LIBC assignment. If supported by >>> diffutils, we might be able to test ENABLE_WIDEC in diffutils and >>> configure accordingly (see the ncurses recipes for an example). >> >> I'll poke around. I'm curious why poky-tiny core-image-minimal built >> OK, but core-image-minimal-initramfs didn't. I didn't expect >> any difference in target-side binaries between the two - only some >> changes in the image build steps. >> >> Thanks for the tips. I'll check it out. > > Let me know what you find out. I thought the initramfs had the installer > in it, but maybe that's included by some other mechanism. Will do. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 10:57 AM, Tim Bird wrote: > On 11/14/2012 10:50 AM, Darren Hart wrote: >> runqemu doesn't quite know what to make of poky-tiny :-) Try the following: >> >> $ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz >> -nographic -append "console=ttyS0 root=/dev/ram0" > > Ahh. That's helpful. Thanks. > >> I really need to get the poky-tiny docs going... right after I finish >> these kernel docs I guess... anyone want to volunteer? > > I'd be happy to write some stuff up. It wouldn't > be exhaustive, but I could document what I've found out about > (the LIBC_FEATURE stuff, and some of the dependencies I've found, > as well as invocation tips and some of the differences between > the poky default and poky-tiny packages and features). > > Where would you like it? Is there a wiki page or a doc already started? Not yet, how about here: https://wiki.yoctoproject.org/wiki/Projects/Poky-Tiny And we'll link to it here: https://wiki.yoctoproject.org/wiki/Projects Thanks for volunteering, very much appreciated! -- Darren > > > Has anyone seen this type of error before, or can provide some > hints of what to check or adjust to fix this? Yup, it's wide characters being required by diffutils and being excluded by the poky-tiny DISTRO_FEATURES_LIBC assignment. If supported by diffutils, we might be able to test ENABLE_WIDEC in diffutils and configure accordingly (see the ncurses recipes for an example). >>> >>> I'll poke around. I'm curious why poky-tiny core-image-minimal built >>> OK, but core-image-minimal-initramfs didn't. I didn't expect >>> any difference in target-side binaries between the two - only some >>> changes in the image build steps. >>> >>> Thanks for the tips. I'll check it out. >> >> Let me know what you find out. I thought the initramfs had the installer >> in it, but maybe that's included by some other mechanism. > > Will do. > -- Tim > > = > Tim Bird > Architecture Group Chair, CE Workgroup of the Linux Foundation > Senior Staff Engineer, Sony Network Entertainment > = > -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 11:05 AM, Darren Hart wrote: > On 11/14/2012 10:57 AM, Tim Bird wrote: >> On 11/14/2012 10:50 AM, Darren Hart wrote: >>> runqemu doesn't quite know what to make of poky-tiny :-) Try the following: >>> >>> $ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz >>> -nographic -append "console=ttyS0 root=/dev/ram0" >> >> Ahh. That's helpful. Thanks. This is working now. Thanks. BTW - how do I stop the kernel/emulator? There's no 'shutdown', and 'halt' and 'reboot' don't do anything. Is there a key sequence to get back to the qemu monitor?? >>> I really need to get the poky-tiny docs going... right after I finish >>> these kernel docs I guess... anyone want to volunteer? >> >> I'd be happy to write some stuff up. It wouldn't >> be exhaustive, but I could document what I've found out about >> (the LIBC_FEATURE stuff, and some of the dependencies I've found, >> as well as invocation tips and some of the differences between >> the poky default and poky-tiny packages and features). >> >> Where would you like it? Is there a wiki page or a doc already started? > > Not yet, how about here: > > https://wiki.yoctoproject.org/wiki/Projects/Poky-Tiny > > And we'll link to it here: > > https://wiki.yoctoproject.org/wiki/Projects > > Thanks for volunteering, very much appreciated! There's some initial stuff there now. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 01:47 PM, Tim Bird wrote: > On 11/14/2012 11:05 AM, Darren Hart wrote: >> On 11/14/2012 10:57 AM, Tim Bird wrote: >>> On 11/14/2012 10:50 AM, Darren Hart wrote: runqemu doesn't quite know what to make of poky-tiny :-) Try the following: $ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz -nographic -append "console=ttyS0 root=/dev/ram0" >>> >>> Ahh. That's helpful. Thanks. > > This is working now. Thanks. > > BTW - how do I stop the kernel/emulator? > There's no 'shutdown', and 'halt' and 'reboot' don't do anything. > Is there a key sequence to get back to the qemu monitor?? Never mind. I figured it out. It's 'ctrl-a ', with 'ctrl-a x' to terminate the qemu session. = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem compiling diffutils on poky-tiny in danny
On 11/14/2012 01:47 PM, Tim Bird wrote: > On 11/14/2012 11:05 AM, Darren Hart wrote: ... I really need to get the poky-tiny docs going... right after I finish these kernel docs I guess... anyone want to volunteer? >>> >>> I'd be happy to write some stuff up. It wouldn't >>> be exhaustive, but I could document what I've found out about >>> (the LIBC_FEATURE stuff, and some of the dependencies I've found, >>> as well as invocation tips and some of the differences between >>> the poky default and poky-tiny packages and features). >>> >>> Where would you like it? Is there a wiki page or a doc already started? >> >> Not yet, how about here: >> >> https://wiki.yoctoproject.org/wiki/Projects/Poky-Tiny >> >> And we'll link to it here: >> >> https://wiki.yoctoproject.org/wiki/Projects >> >> Thanks for volunteering, very much appreciated! > > There's some initial stuff there now. This is awesome Tim, thank you very much! I moved it to https://wiki.yoctoproject.org/wiki/Poky-Tiny as that is more consistent with the other Project pages (which became apparent when I saw the Projects/Poky-Tiny link on the main Projects page). Sorry for the bad info above. A couple points to consider. 1) You might want to add tiny-init as being a integral part of poky-tiny 2) You can also inherit from poky tiny using "include poky-tiny.conf" rather than duplicating it wholesale. You can then update things like the various DISTRO_LIBC_* items to adjust how libc is built, and otherwise keep your tiny distribution definition small and make it easier to maintain (so long as you want to continue to inherit changes made to poky-tiny). Again, thank you for doing this! -- Darren > -- Tim > > = > Tim Bird > Architecture Group Chair, CE Workgroup of the Linux Foundation > Senior Staff Engineer, Sony Network Entertainment > = > -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Nightly Build for Weekly Testing
We have done nightly build, while it's showing red the failures are due to a shared state issue which Richard fixed quickly. The build was done with the commit prior to what I list here. This is to ensure we have Richard's sstate version bump and won't see these issue. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9e0d3c0faa9cc80ce8f2ce0eb31dcd20ef875955 This contains the build artifacts. http://autobuilder.yoctoproject.org/pub/nightly/20121114-1/machines/ Please do standard weekly testing. Thanks Sau! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
