[yocto] Distribution verification
Hi I'm running the upcomming Ubuntu 14.10, how can I help making that version a tested distrubution? -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] MIPI for Intel E3800 Bay Trail
I don't know what MIPI is but the Baytrail platform is supported from v3.13 as far as I remember. Tirsdag den 8. juli 2014 12:14:10 skrev Rudolf Streif: This question is lesser a matter of YP but probably of upstream support. Nevertheless, the YP kernel experts would certainly know. Which, if any, of the YP kernels provide MIPI drivers for the Intel E3800? Thanks, Rudi -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] File system for alternate partition
Hi Make bitbake give you a tar.bz2 and then create the partitions etc. yourself using an additional script. Wether it could be integrate I do not know. Mandag den 23. juni 2014 11:59:30 skrev Bollinger, Seth: Hello All, I need to generate a new file system for an alternate partition (not rootfs). What’s the best way to go about this? I may need to create files with all different users/permission (perhaps root). Do I need to use pseudo? Are there any examples of this out there? -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problems creating recipe, no package provides
Hi
I guess the file should be named libmongoose_5.3.bb and not
libmongoose-5.3.bb
Tirsdag den 17. juni 2014 12:30:36 skrev Henric Eriksson:
Hello,
I've been working on creating a recipe for the library mongoose for use
in a custom layer in Yocto. The library provides a .so in /usr/lib and a
.h in /usr/include and is depended (DEPENDS=libmongoose) on in another
recipe for a my main application. When trying to bitbake my image though
it fails on the last stage do_rootfs.
The recipe is quite simple:
libmongoose-5.3.bb:
-
DESCRIPTION = Mongoose is the most easy to use web server on the planet
SECTION = libs
LICENSE = GPLv2
HOMEPAGE = http://code.google.com/p/mongoose;
LIC_FILES_CHKSUM =
file://${COREBASE}/meta/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe
PR = r0
SRC_URI = git://github.com/cesanta/mongoose.git
SRCREV = 30a79651356e28fec240e921f8cd01c9a0a21388
S = ${WORKDIR}/git
CFLAGS += -W -Wall -I.. -pthread -g -pipe -fpic
do_compile() {
${CC} ${CFLAGS} -c mongoose.c -o mongoose.o
${CC} -shared -o libmongoose.so mongoose.o
}
do_install() {
install -d ${D}${libdir}
install -d ${D}${includedir}
install -m 0755 libmongoose.so ${D}${libdir}
install -m 0755 mongoose.h ${D}${includedir}
}
-
Eventually though during do_rootfs, this error pops up:
error: Can't install libmongoose-dev-5.3-r0@armv5te: no package provides
libmongoose = 5.3-r0
I have tried to add both PACKAGES += libmongoose and PACKAGES +=
libmongoose-dev in the recipe but nothing seems to help.
Looking through Yocto I can see that it appends -dev and such based on
what files are provided by the package. But I guess since all the files
from the package is provided by libmongoose-dev it dumps libmongoose.
I'm at a loss of where to go from here. What have I missed in my recipe?
Regards,
Henric Eriksson
--
Søren Holm
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problems with postinstall
Hi
postinstall is afaik run during installation. And that could very well be on
the actual target. So ${S} etc. are not available. The step is just for steps
that *need* to run on the actual target utilizing the files that where install
in do_install.
Fredag den 6. juni 2014 08:16:39 skrev Neuer User:
Nobody using any postinstalls?
I am still wondering why the postinstall does not work. I don't get any
error messages. The files are just not installed.
Am 05.06.2014 12:44, schrieb Neuer User:
Hi
I am desperately trying to get some postinstall scripts working. They
should replace some defualt files with custom files I have. They are all
in one package. The package looks like this:
do_install() {
install -d ${D}${sbindir}
install -m 0700 ${S}/sbin/* ${D}${sbindir}
install -d ${D}${bindir}
install -m 0755 ${S}/bin/LEDstatus ${D}${bindir}
install -d ${D}/etc/udev/rules.d
install -m 0644 ${S}/udev/* ${D}/etc/udev/rules.d/
install -d ${D}/etc/ssh
install -m 0600 ${S}/ssh/ssh_* ${D}/etc/ssh/
install -m 0644 ${S}/ssh/authorized_keys ${D}/etc/ssh/
install -d ${D}/etc/gnupg
install -m 0600 ${S}/gnupg/trustedkeys.gpg ${D}/etc/gnupg/
}
# Overwrite some configuration data with specific files
pkg_postinst_${PN} () {
install -o root -g root -m 0600 ${S}/ssh/sshd_config ${D}/etc/ssh/
install -m 0755 ${S}/etc/rc.local ${D}/etc/
install -m 0644 ${S}/etc/watchdog.conf ${D}/etc/
install -m 0400 ${S}/etc/shadow ${D}/etc/
install -m 0440 ${S}/etc/sudoers ${D}/etc/
install -d ${D}/etc/default
install -o root -g root -m 0644 ${S}/etc/default-ntpdate
${D}/etc/default/ntpdate
}
RDEPENDS_${PN} += ntpdate udev ssh sudo
FILES_${PN} += /*
I even tried changing the ownership of the files, but that did not
change aything.
Am I doing this completely wrong?
Thanks for any hints
Michael
--
Søren Holm
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto with Initial RamFS
Torsdag den 29. maj 2014 08:07:11 skrev Brian Smucker:
Hi,
Was wondering why this has not been answered. Maybe it is too dumb of a
question? If so, let me know or point me to some documentation.
I'm declaring an initramfs-image like this. As you can see the recipe is
derived from core-image-minimal-initramfs. The package initramfs-vm provides
the script /init executed on boot.
The assembling of the actual bootable image with initramfs and rootfs (in my
case a squashfs) is done in another script.
# initramfs for vm-image. Derived from core-image-minimal-initramfs
DESCRIPTION = Small image capable of booting a a squashfs+aufs filesystem
IMAGE_INSTALL = initramfs-vm-boot busybox udev base-passwd
# Do not pollute the initrd image with rootfs features
IMAGE_FEATURES =
IMAGE_LINGUAS =
#DISTRO_FEATURES =
inherit core-image
IMAGE_FSTYPES = cpio
IMAGE_PREPROCESS_COMMAND = cb16_remote_bloat;
cb16_remote_bloat() {
rm -r ${IMAGE_ROOTFS}/boot
}
--
Søren Holm
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto with Initial RamFS
Torsdag den 29. maj 2014 09:49:55 skrev Brian Smucker: Thanks Soren, My followup question is: Can I mix toolchains in this situation? Can I compile the initramfs binaries with the uclibc toolchain based on the poky-tiny distro and the regular file system binaries with the glibc-based toolchain (based on a different distro)? If this is possible, how would I begin to do it? I don't know, but I've got a simmilar need. Basically I was a very minimal busybox-static for the initramfs, but a full-fledged version for the main rootfs. I guess that's somehow the same thing. Maybe you have an idea on how to do that? -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] replace udhcpc
Use ifplugd recipe I just submitted. Onsdag den 7. maj 2014 10:57:22 skrev Neuer User: Hi I encounter a problem with the DHCP network setup during boot: System starts. During start ifup is called. ifup calls udhcpc. Network is, however, not yet up! udhcpc exits with failure. Then network is up. But, of course, no connection, because no IP address. In earlier times I used debian based system, which seem to rely on dhclient3. My experiences here were that dhclient remained as a deamon continuing trying to get a dhcp address. What should I do best on Yocto? Replace udhcpc with dhclient? If so, how should that be done? Or can udhcpc be configured to remain in the background and try to get an IP address when network is finally up? Thanks for any help Michael -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-networking][PATCH] ifplugd: Added ifplugd recipe.
Signed-off-by: Søren Holm s...@sgh.dk
---
.../ifplugd/files/ifplugd.conf | 42 ++
.../recipes-connectivity/ifplugd/ifplugd_0.28.bb | 23
2 files changed, 65 insertions(+)
create mode 100644
meta-networking/recipes-connectivity/ifplugd/files/ifplugd.conf
create mode 100644 meta-networking/recipes-connectivity/ifplugd/ifplugd_0.28.bb
diff --git a/meta-networking/recipes-connectivity/ifplugd/files/ifplugd.conf
b/meta-networking/recipes-connectivity/ifplugd/files/ifplugd.conf
new file mode 100644
index 000..1e0f83a
--- /dev/null
+++ b/meta-networking/recipes-connectivity/ifplugd/files/ifplugd.conf
@@ -0,0 +1,42 @@
+# -*-sh-*-
+# $Id: ifplugd.conf 43 2003-09-13 11:25:11Z lennart $
+
+# This file is part of ifplugd.
+#
+# ifplugd is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free
+# Software Foundation; either version 2 of the License, or (at your
+# option) any later version.
+#
+# ifplugd is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
+# for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with ifplugd; if not, write to the Free Software Foundation,
+# Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
+
+# ifplugd configuration file
+
+# Please note that this is a bourne shell fragment sourced by the
+# init script of ifplugd.
+
+# Specify the interfaces to control here, separated by spaces.
+# Ifplugd processes will be started for each of these interfaces when
+# the ifplugd init script is called with the start argument. You may
+# use the magic string auto to make the init script start or stop
+# ifplugd processes for ALL eth and wlan interfaces that are available
+# according to /proc/net/dev. Note that the list of interfaces
+# appearing in /proc/net/dev may depend on which kernel modules you
+# have loaded.
+INTERFACES=eth0
+
+# Additional parameters for ifplugd.
+# (Run ifplugd -h for further information.)
+ARGS=-fwI -u0 -d10
+
+# Additional parameters for ifplugd for the specified interface. Note
+# that $ARGS is ignored, when a variable like this is set for an
+# interface
+#ARGS_wlan0=-MwI -u5 -d5
diff --git a/meta-networking/recipes-connectivity/ifplugd/ifplugd_0.28.bb
b/meta-networking/recipes-connectivity/ifplugd/ifplugd_0.28.bb
new file mode 100644
index 000..340d5f4
--- /dev/null
+++ b/meta-networking/recipes-connectivity/ifplugd/ifplugd_0.28.bb
@@ -0,0 +1,23 @@
+DESCRIPTION = Daemon for monitoring ethernet device link state
+SRC_URI = http://0pointer.de/lennart/projects/ifplugd/ifplugd-0.28.tar.gz
\
+ file://ifplugd.conf
+DEPENDS = libdaemon
+LICENSE = GPLv2
+
+LIC_FILES_CHKSUM = file://LICENSE;md5=94d55d512a9ba36caa9b7df079bae19f
+
+SRC_URI[md5sum] = df6f4bab52f46ffd6eb1f5912d4ccee3
+SRC_URI[sha256sum] =
474754ac4ab32d738cbf2a4a3e87ee0a2c71b9048a38bdcd7df1e4f9fd6541f0
+
+EXTRA_OECONF_append = --disable-lynx
+
+
+INITSCRIPT_PACKAGES = ${PN}
+INITSCRIPT_NAME_${PN} = ${PN}
+INITSCRIPT_PARAMS_${PN} = defaults 90
+
+do_install_append() {
+ install -m 644 ${WORKDIR}/ifplugd.conf ${D}${sysconfdir}/ifplugd/
+}
+
+inherit autotools update-rc.d
\ No newline at end of file
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Hi Bruce I've search the meta-data repos and kernel repo for a change matching this. Is it fixes or did you miss it? Fredag den 11. april 2014 15:05:56 skrev Bruce Ashfield: I am. There's a missing patch that I typically carry, it actually links the fs/aufs directory into the build. Without it, the Kconfig and code isn't processed .. hence why everything is dropped. I have it merged now, but have to build aufs for all architectures to make sure nothing broke. -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Thanks Richard. Tirsdag den 22. april 2014 09:46:04 skrev Richard Purdie: On Tue, 2014-04-22 at 08:13 +0200, Søren Holm wrote: Hi Bruce I've search the meta-data repos and kernel repo for a change matching this. Is it fixes or did you miss it? The change is: http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=zedd/kernelid=a 112c85c02f161dc03bf71cdb9d2b3557999bbfd It didn't make it into the 1.6 release branch, it will go in for 1.6.1 and is queued for there and master. Cheers, Richard -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Sure I guess this is what you need : http://sgh.dk/~sgh/cb16_kernel.tar.bz2 It's just the machine-configuration and my append-file and defconfig. Fredag den 11. april 2014 00:19:15 skrev Bruce Ashfield: Nothing has changed in this area, and it works here. Can you post your defconfig, and machine you are building somewhere so I can try it myself ? Bruce -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Hi Bruce I just check if AUFS is enabled. It should be since that's in my defconfig. Fredag den 11. april 2014 09:49:29 skrev Bruce Ashfield: On 14-04-11 03:39 AM, Søren Holm wrote: Sure I guess this is what you need : http://sgh.dk/~sgh/cb16_kernel.tar.bz2 It's just the machine-configuration and my append-file and defconfig. replying again .. with the list this time. Great. I did a build here and I see the defconfig being applied. How were you determining that it wasn't happening ? I want to make sure I'm checking the same config options. -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Hi Bruce I just realized that I gave you the wrong files. I migrate to dora, so 3.14 is my kernel I'm building. I gave you the dora-files - doh!. I'll check if 3.10 works because it does for you on daisy and for me on dora. Fredag den 11. april 2014 11:05:44 skrev Bruce Ashfield: On 14-04-11 11:03 AM, Søren Holm wrote: Hi Bruce I just check if AUFS is enabled. It should be since that's in my defconfig. -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Ok Using the *exact* same bbappend file for both 3.10 and 3.14 gives me a correct -config for 3.10 but not for 3.14. Both 3.10/defconfig and 3.14/defconfig contains my original defconfig, so it is picked up and should be taken into account. Fredag den 11. april 2014 11:24:10 skrev Bruce Ashfield: On 14-04-11 11:21 AM, Søren Holm wrote: Hi Bruce I just realized that I gave you the wrong files. I migrate to dora, so 3.14 is my kernel I'm building. I gave you the dora-files - doh!. I'll check if 3.10 works because it does for you on daisy and for me on dora. No worries. I just forced the kernel version to 3.10 to test. If you want to send the 3.14 ones, I can double check there as well. Bruce Fredag den 11. april 2014 11:05:44 skrev Bruce Ashfield: On 14-04-11 11:03 AM, Søren Holm wrote: Hi Bruce I just check if AUFS is enabled. It should be since that's in my defconfig. -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] defconfig on daisy
Hi Bruce That sounds great. The situation is that I though that that was the case, so I also tried adding this to the bbappend. KERNEL_FEATURES_append = features/aufs But that does not seem to work either. So I guess you are talking about somthing else. Fredag den 11. april 2014 12:51:01 skrev Bruce Ashfield: On 14-04-11 12:15 PM, Søren Holm wrote: Ok Using the *exact* same bbappend file for both 3.10 and 3.14 gives me a correct -config for 3.10 but not for 3.14. Both 3.10/defconfig and 3.14/defconfig contains my original defconfig, so it is picked up and should be taken into account. This is a slightly different problem .. I can see that I managed to drop a patch which links AUFS into the build. Hence why everything is dropped. I'm fixing that right now in 3.14, and will send updates later. -- Søren Holm -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] defconfig on daisy
Hi
I have a linux-yocto_3.14.bbappend file in my local layer. Basically it just
specifies the defconfig for the kernel.
The problem now is just that defconfig is not used for the specific kernel.
It's copied into ${WORKDIR} but never used.
Have procedures on how to do this changed since dora - or is somthing broken?
--
Søren Holm
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Constant linux-yocto rebuild
Hi I'm having a weird issue with dora. After having rebuild everything from scratch I usually rebuild some of my own applications and rebuild the image recipe to create the image. This all works great. But then after some number of rebuild linux-yoc suddenly gets rebuild every time. Even two consequtive builds of my image recipe give me two linux-yocto rebuild. Any hint on what might happen or what I can do to debug it? -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Constant linux-yocto rebuild
Wow - that was a quick response. Is it the two by Mike Crowe ? And do they get into dora at some point? Søndag den 12. januar 2014 14:38:57 skrev Martin Jansa: On Sun, Jan 12, 2014 at 02:19:51PM +0100, Søren Holm wrote: Hi I'm having a weird issue with dora. After having rebuild everything from scratch I usually rebuild some of my own applications and rebuild the image recipe to create the image. This all works great. But then after some number of rebuild linux-yoc suddenly gets rebuild every time. Even two consequtive builds of my image recipe give me two linux-yocto rebuild. Any hint on what might happen or what I can do to debug it? You need patch 3 and 4 from http://lists.openembedded.org/pipermail/openembedded-core/2014-January/08807 4.html -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto and ccache
I don't think it's necessary to explicitly use ccache since the OE/Yocto framework already provides a sstate.bbclass which implements this sort of logic and is designed to work better with the sorts of things bitbake does: Yes, it does only cache complete compiled and packed recipes. My workflow will many times be tat I compile the same software with minor changes. And since it is always from scratch it will always take the same amount of time. Basically I use Jenkins for rebuilding my image and specific recipes are then tracking a branch in my application. -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto and ccache
Hi I've search the manual and google for some time now in relation to yocto and ccache. So the question is now: How to I make yocto utilize ccache - it does not seem to do it on it's own? -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to force the use of git-native?
Hi Should'nt it be enough to remove git-native from ASSUME_PROVIDED ? Mandag den 16. december 2013 10:33:17 skrev Gary Thomas: On 2013-12-16 08:10, Flanagan, Elizabeth wrote: Gary: This should help. http://autobuilder.yoctoproject.org/pub/buildtools/20131216-2/buildtools/p oky-eglibc-i686-buildtools-tarball-i586-buildtools-nativesdk-standalone-1. 5.sh I haven't tested this out yet, but it is based off of the dora 10.0.0 release, so please, let me know if you have problems with it. Seems to work fine on my Fedora 13 box. -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto .gitignore
Mandag den 2. december 2013 11:57:35 skrev Paul Eggleton: I presume you mean the .gitignore in the poky repository. Any additional custom layers shouldn't be part of the poky repository, they should be in separate repositories. That's right. But how would you put build/* and my own meta-* in a seperate repo. Pulling them in as submodules seems painfull and having the yocto-repo included as a submodule in another repo seems backwards too. Do you have a proposed best-practice-way of maintaining own layers? -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto .gitignore
Hi Why does yocto .gitignpre include meta-*/. Why would we possibly want to ignore custom layers ? -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Console charset
Hi Im trying to set the console charset to utf8, but I can figure our which packages are needed. Can you provide some hint of where to look. I have this in my local.conf, but it's not al all enough. GLIBC_GENERATE_LOCALES = en_GB.UTF-8 en_US.UTF-8 da_DK.UTF-8 IMAGE_LINGUAS = da-dk en-us -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mono] Question about Q/A installed vs shipped failure
Fredag den 1. november 2013 10:03:44 skrev Alex J Lennon:
Hi,
I'm looking at at the gtk-sharp recipe in meta-mono:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/gtk-sh
arp/gtk-sharp_2.10.2.bb
This defines the contents of various gtk-sharp related packages making
use of FILES_foo = and PACKAGES =
When I try to build against the Yocto head it fails a Q/A check with
ERROR: QA Issue: gtk-sharp: Files/directories were installed but not
shipped
Normally I would expect the extraneous files to be found in the image
tree and add do_install_append() to rm the unneeded files from {$}D/foo/bar
However the behaviour of this recipe seems different.
For some reason the extraneous files are being found in the ../package
tree. They are put there by the do_package() step, which is executed
after my do_install_append().
I have expecienced a simillar behaviour while building an application using
qmake. In my case all the source-files where for some reason copied into the
package-directory like you descrive.
I have tried adding a do_package_append() which I thought might help but
bitbake won't accept this.
Can anybody advise:
(a) if files being in ./package indicates a problem with the recipe or
if this is correct behaviour, and
(b) what is recommended practice to deal with this?
For now I am adding INSANE_SKIP_${PN} = installed-vs-shipped to the
recipe but I'd rather not disable Q/A in this manner.
I did the same thing.
Thanks,
Alex
--
Søren Holm
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] e2fsprogs: Escape filenames in populate-extfs.sh
Fredag den 1. november 2013 11:11:52 skrev Burton, Ross: Please sent patches to oe-core@. Should patches be sent to oe-core only or should they also be sent to yocto? -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] 2.6.39 kernel and poky
You could try to copy the 3.10 recipe and just fixc the revision to point to the old version. the kernels buildsystem have not changes dramatically since then I think/hope :) Fredag den 1. november 2013 11:21:39 skrev Maxwell Bottiger: I have a custom kernel and drivers I built for an Atmel AT91SAM9x5ek system on a chip, and I'd like to use them with yocto to build a distribution. The original documentation, support CD, etc are all based around an open embedded build from 2011, which doesn't seem to work any longer. Yocto looks like a great alternative, but wants to build the 3.10 kernel, which I don't think supports this SoC any longer. So, is there a straight forward method of building a standard Poky root filesystem, but with a custom recipe for the 2.6.39 kernel instead of the stock one? Thanks for your help. -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappend files and ERROR: no recipes available for
Hi
Rename your bbappend-file to the exact name of the original recipe.
1.5 (dora) contains linux-firmware_git.bb in which case the bbappend should be
named linux-firmware_git.bbappend.
Fredag den 1. november 2013 15:43:19 skrev Markus Svilans:
Dear list,
I am working on a compact filesystem image, that contains firmware only
for the network hardware on the motherboard.
Therefore, I created a linux-firmware.bbappend file, with the following
contents:
# Cherrypick the firmware files that we need for our hardware
#FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
PACKAGES += ${PN}-rtl8168d-1
FILES_${PN}-rtl8168d-1 = \
/lib/firmware/rtl_nic/rtl8168d-1.fw \
However, running bitbake linux-firmware fails with this bbappend file
present:
ERROR: No recipes available for:
/home/markus/yocto/genericx86-64-dora-10.0.0/meta-markus/recipes-kernel/li
nux-firmware/linux-firmware.bbappend ERROR: Command execution failed:
Exited with 1
Other bbappend files, such as for custom kernel config for linux-yocto,
worked without complaints.
So far, I was following the instructions for using bbappend files here:
http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#using-bbappe
nd-files http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html
From what I can see, I am setting up my linux-firmware.bbappend file
consistently with the instructions.
What am I doing wrong here?
Thanks very much
Markus
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Søren Holm
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Trouble packaging files containing space
Hi
I have a package containing files that includes spaces in their same.
The files are located in the same directory without a space in their name is
packages just find.
I specify FILES_$[PN} like this
FILES_${PN} = ${prefix}/local/Mikrofyn
What might be wrong?
--
Søren Holm
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trouble packaging files containing space
Mandag den 28. oktober 2013 16:01:24 skrev Paul Eggleton: Søren, are you getting unpackaged file warnings? Are the files listed if you look under image/ in the work directory for the recipe? FWIW, I just tested here and installing files whose filenames contain spaces worked just fine. I get erro regarding files installed but not shipped - but that's a differen issue I think. That particular issue is strange sine the un-shupped files are source-files that I do not install. They end up in image/ during do_package. The image-dir contains all the files including the files containing spaces. -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trouble packaging files containing space
Mandag den 28. oktober 2013 16:17:46 skrev Paul Eggleton:
On Monday 28 October 2013 17:05:54 Søren Holm wrote:
Mandag den 28. oktober 2013 16:01:24 skrev Paul Eggleton:
Søren, are you getting unpackaged file warnings? Are the files listed if
you look under image/ in the work directory for the recipe? FWIW, I just
tested here and installing files whose filenames contain spaces worked
just fine.
I get erro regarding files installed but not shipped - but that's a
differen issue I think. That particular issue is strange sine the
un-shupped files are source-files that I do not install. They end up in
image/ during do_package.
The image-dir contains all the files including the files containing
spaces.
I think I might need some more details - can you please paste the actual
error, the relevant parts of the recipe and a directory listing under
image/${prefix}/local ?
Having a recipe containing just this works. I'll try stripping my original
much larger recipe to see what breaks it.
do_install() {
touch ${D}/file with spaces.txt
}
FILES_${PN} = /
--
Søren Holm
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] e2fsprogs: Escape filenames in populate-extfs.sh
[YOCTO #5401] --- .../e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh b/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh index 9eff030..7de720b 100644 --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh @@ -35,7 +35,7 @@ DEBUGFS=debugfs fi # Only stat once since stat is a time consuming command - STAT=$(stat -c TYPE=\%F\;DEVNO=\0x%t 0x%T\;MODE=\%f\;U=\%u\;G=\%g\ $FILE) + STAT=$(stat -c TYPE=\%F\;DEVNO=\0x%t 0x%T\;MODE=\%f\;U=\%u\;G=\%g\ $FILE) eval $STAT case $TYPE in @@ -43,20 +43,20 @@ DEBUGFS=debugfs echo mkdir $TGT ;; regular file | regular empty file) - echo write $FILE $TGT + echo write \$FILE\ \$TGT\ ;; symbolic link) - LINK_TGT=$(readlink $FILE) - echo symlink $TGT $LINK_TGT + LINK_TGT=$(readlink $FILE) + echo symlink \$TGT\ \$LINK_TGT\ ;; block special file) - echo mknod $TGT b $DEVNO + echo mknod \$TGT\ b $DEVNO ;; character special file) - echo mknod $TGT c $DEVNO + echo mknod \$TGT\ c $DEVNO ;; fifo) - echo mknod $TGT p + echo mknod \$TGT\ p ;; *) echo Unknown/unhandled file type '$TYPE' file: $FILE 12 @@ -64,11 +64,11 @@ DEBUGFS=debugfs esac # Set the file mode - echo sif $TGT mode 0x$MODE + echo sif \$TGT\ mode 0x$MODE # Set uid and gid - echo sif $TGT uid $U - echo sif $TGT gid $G + echo sif \$TGT\ uid $U + echo sif \$TGT\ gid $G done # Handle the hard links. -- 1.8.3.2 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] e2fsprogs: Escape filenames in populate-extfs.sh
Hi I'm reposting my patch as a response tot this message. I forgot adding some actual description of why the change is necessary. Sorry. I would like the change to go into dora if possible. -- Søren Holm ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] e2fsprogs: Escape filenames in populate-extfs.sh
Without this patch filenames containing spaces do not get into the final ext2/3/4 filsystem. [YOCTO #5401] --- .../e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh b/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh index 9eff030..7de720b 100644 --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh @@ -35,7 +35,7 @@ DEBUGFS=debugfs fi # Only stat once since stat is a time consuming command - STAT=$(stat -c TYPE=\%F\;DEVNO=\0x%t 0x%T\;MODE=\%f\;U=\%u\;G=\%g\ $FILE) + STAT=$(stat -c TYPE=\%F\;DEVNO=\0x%t 0x%T\;MODE=\%f\;U=\%u\;G=\%g\ $FILE) eval $STAT case $TYPE in @@ -43,20 +43,20 @@ DEBUGFS=debugfs echo mkdir $TGT ;; regular file | regular empty file) - echo write $FILE $TGT + echo write \$FILE\ \$TGT\ ;; symbolic link) - LINK_TGT=$(readlink $FILE) - echo symlink $TGT $LINK_TGT + LINK_TGT=$(readlink $FILE) + echo symlink \$TGT\ \$LINK_TGT\ ;; block special file) - echo mknod $TGT b $DEVNO + echo mknod \$TGT\ b $DEVNO ;; character special file) - echo mknod $TGT c $DEVNO + echo mknod \$TGT\ c $DEVNO ;; fifo) - echo mknod $TGT p + echo mknod \$TGT\ p ;; *) echo Unknown/unhandled file type '$TYPE' file: $FILE 12 @@ -64,11 +64,11 @@ DEBUGFS=debugfs esac # Set the file mode - echo sif $TGT mode 0x$MODE + echo sif \$TGT\ mode 0x$MODE # Set uid and gid - echo sif $TGT uid $U - echo sif $TGT gid $G + echo sif \$TGT\ uid $U + echo sif \$TGT\ gid $G done # Handle the hard links. -- 1.8.3.2 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
