[yocto] libc6-dbg-2.20-r0.core2_64.rpm empty
Hello, I'm trying to use Valgrind but when I start it, it gives me an error because a required library has its symbols stripped. After looking around, I found out that the libc6-dbg packages should be installed and it is. However, when I look into the rpm for libc6-dbg, it is empty. Why is that? What must I do so it contains the non-strip version of the library? Thank you. François Gallichand Engineer - Software Group ABB Group Analytical Business (418)877-2944 x268 [ABB logo] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USBmount and systemd-udev namespace conflict
Hello, I finally found a solution to my problem. In fact, the mounts made by udevd not being accessible to other processes comes from the way the system-udevd service is started. In the /lib/systemdsystem/system-udevd.service, I just remove the MountFlags=slave line and by doing that, all the mounts are shared (the default) and accessible by all the processes. Regards, François Gallichand Engineer - Software Group ABB Group Analytical Business (418)877-2944 x268 [ABB logo] From: Li, Xin [mailto:lixin.f...@cn.fujitsu.com] Sent: Monday, December 15, 2014 8:23 PM To: Francois P. Gallichand; yocto@yoctoproject.org Subject: RE: USBmount and systemd-udev namespace conflict Hi, This is my way to use udev to automount a usb driver, perhaps it can help you. 1. Add udev rules. root # cat /etc/udev/rules.d/10-udevtest.rules KERNEL==sda,ACTION==add,OWNER:=udev,GROUP:=udevs 2. Add user and group. root # useradd udev root # groupadd udevs 3. start the udev service root # systemctl start systemd-udevd.service root # ps aux | grep udev root 21927 0.3 0.0 26140 1388 ?Ss 22:51 0:00 /lib/systemd/systemd-udevd 4. insert usb driver 5. check root # ls /dev/sda -al brw-rw 1 udev udevs 8, 0 Sep 15 03:13 /dev/sda - Best regards, Li From: yocto-boun...@yoctoproject.orgmailto:yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Francois P. Gallichand Sent: Tuesday, December 16, 2014 3:34 AM To: yocto@yoctoproject.orgmailto:yocto@yoctoproject.org Subject: [yocto] USBmount and systemd-udev namespace conflict Hello, I need to automount a usb drive when it is plugged in. I found that the necessary udev rules are in the udev-extraconf package so I added that to my build. I tried it but it does not really work since when I insert the key, it is in fact mounted by udev but since the mount namespace of udev is private and not the same one as the shell I want to check if the key is mounted, I don’t see it. Is there a way to tell udev to mount using a global namespace so it can be seen be everybody? Thanks. François Gallichand Engineer - Software Group ABB Group Analytical Business (418)877-2944 x268 [ABB logo] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] USBmount and systemd-udev namespace conflict
Hello, I need to automount a usb drive when it is plugged in. I found that the necessary udev rules are in the udev-extraconf package so I added that to my build. I tried it but it does not really work since when I insert the key, it is in fact mounted by udev but since the mount namespace of udev is private and not the same one as the shell I want to check if the key is mounted, I don't see it. Is there a way to tell udev to mount using a global namespace so it can be seen be everybody? Thanks. François Gallichand Engineer - Software Group ABB Group Analytical Business (418)877-2944 x268 [ABB logo] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Error when copying the same file from two different packages/recipes with version 1.7
Hello,
In a custom recipe I wrote, I want to replace a file that is already added by
another package/recipe. I know that normally the proper way to do that would be
to use a .bbappend recipe for the original recipe that installs this file and
in this .bbappend, copy my version of the file; but this method does not
achieve exactly what I want to do since I want to replace the file only when I
include my recipe in the resulting build but keep the file from the original
package/recipe if I don't include my recipe. So what I did is to add the file I
want into my recipe and copy it at the same location where the original
package/recipe puts it; then I added a RDEPENDS_${PN} = original package in
my recipe so my file gets copied last, thus overwriting the file from the
original package/recipe. This was working with version 1.6 of Yocto but with
version 1.7, it gives an error saying that it does know how to handle the
problem. It also suggest possible solutions to correct the problem. The one
that I think I could use is about adding the problem file (or packages?) to the
STATE_DUPWHITELIST. I am not sure if it is really the best solution or even how
to apply it because I haven't found any documentation about this
STATE_DUPWHITELIST.
Could someone tell how to use this STATE_DUPWHITELIST? Is it the way to go to
solve my problem or is there a better way to do that?
Thank you.
François Gallichand
Engineer - Software Group
ABB Group
Analytical Business
(418)877-2944 x268
[ABB logo]
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding files to the hddimg
Hello Anders, I don't want to copy files into the rootfs, I know how to do that. It's really in the hddimg that I need to copy files, at the same level as the rootfs. To make a short story, here's what I want to do. I want to use a usb drive to install a system so I dd the hddimg to this usb drive. The idea is to boot this usb drive on the target system so it can be used to accomplish various task, like installing a new system or updating or configuring an existing one. So to do that, I need to put the required files to install or configure the system also on the key. You could argue that I can still do all of this even if I put everything in the rootfs. However, I use squashfs for the rootfs (to save space), and also the files on the key must be modifiable by a user using a Windows computer (which is easy since this is a VFAT partition but not the rootfs that's not even writable). Like I mentionned in previous email, one way to achieve that is to extend the bootimg.bbclass, but I tried that and it didn't work (and I don't know why). After talking to some people, I guess that the simple solution is to write a separate script that does what I need i.e.once I build the hddimg, it just mount the hddimg and copy the required stuff on it. It's just that I would have liked to do that in the Yocto environment, but it's no big priority. The resulting real question however is how to extend a .bbclass and why what I tried before didn't work? Any idea about that? Regards, Francois De : Anders Darander and...@chargestorm.se Envoyé : 23 juin 2014 08:26 À : Francois P. Gallichand Cc : Paul Eggleton; yocto@yoctoproject.org Objet : Re: [yocto] Adding files to the hddimg * Francois P. Gallichand francois.p.gallich...@ca.abb.com [140618 19:22]: Thanks for the reply. But that's not really what I want to achieve. Really, I just want to copy some files into the .hddimg file that is built as a result of running bitbake. Like I said, I tried to extend the bootimg.bbclass, which is responsible for creating the .hddimg file, but it's not working and I don't know why. Well, then I guess the question if what kinds of file is it, and how do you want to copy them into the .hddimg? Should they be copied into the rootfs in the .hddimg? If so, I'd suggest to create a standard bitbake recipe and just install those files into the rootfs. If it's something else, I think you need to explain it a little bit more. Cheers, Anders Any suggestions? -- Anders Darander ChargeStorm AB / eStorm AB -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding files to the hddimg
Hello All,
I realized that I may not have been specific enough on my problem since I
haven't had any reply or found a solution yet.
Essentially, I need to be able to add some files to the image file itself
(.hddimg, not the rootfs) and be able to do that automatically (and ideally
from a custom recipe).
What I have tried so far is to extend the bootimg.bbclass. So I created my own
class, myclass.bbclass, with the following content:
Inherit bootimg
myclass_do_bootimg() {
do_bootimg
cp some files ${HDDDIR}
}
EXPORT_FUNCTIONS do_bootimg
And I patched image-live.bbclass to replace the inherit bootimg by inherit
myclass (I don't know if there is a better way to do that?). But it seems that
myclass_do_bootimg is never called, but do_bootimg is.
I also tried the following myclass.bbclass without any more success.
Inherit bootimg
do_some_function() {
cp some files ${HDDDIR}
}
addtask some_function after do_booimg
Can someone tell me what I'm doing wrong?
Thanks for any help.
Francois
François Gallichand
Engineer - Software Group
ABB Group
Analytical Business
(418)877-2944 x268
[ABB logo]
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Francois P Gallichand
Sent: Friday, June 13, 2014 9:58 AM
To: yocto@yoctoproject.org
Subject: [yocto] Adding files to the hddimg
Hello,
I'm relatively new to yocto and this is maybe something that is pretty basic
but how can I add my own files in the bootimg (.hddimg) using a custom recipes?
And I really means the boot image file, not the rootfs image.
Thanks,
François Gallichand
Engineer - Software Group
ABB Group
Analytical Business
(418)877-2944 x268
[ABB logo]
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding files to the hddimg
Hello Paul,
Thanks for the reply. But that's not really what I want to achieve. Really, I
just want to copy some files into the .hddimg file that is built as a result of
running bitbake. Like I said, I tried to extend the bootimg.bbclass, which is
responsible for creating the .hddimg file, but it's not working and I don't
know why.
Any suggestions?
Regards,
Francois
François Gallichand
Engineer - Software Group
ABB Group
Analytical Business
(418)877-2944 x268
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Wednesday, June 18, 2014 12:43 PM
To: Francois P. Gallichand
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Adding files to the hddimg
Hi Francois,
On Wednesday 18 June 2014 15:42:08 Francois P. Gallichand wrote:
I realized that I may not have been specific enough on my problem
since I haven't had any reply or found a solution yet.
Essentially, I need to be able to add some files to the image file
itself (.hddimg, not the rootfs) and be able to do that automatically
(and ideally from a custom recipe).
What I have tried so far is to extend the bootimg.bbclass. So I
created my own class, myclass.bbclass, with the following content:
Inherit bootimg
myclass_do_bootimg() {
do_bootimg
cp some files ${HDDDIR} }
EXPORT_FUNCTIONS do_bootimg
And I patched image-live.bbclass to replace the inherit bootimg by
inherit myclass (I don't know if there is a better way to do that?).
But it seems that myclass_do_bootimg is never called, but do_bootimg is.
I also tried the following myclass.bbclass without any more success.
Inherit bootimg
do_some_function() {
cp some files ${HDDDIR} }
addtask some_function after do_booimg
Can someone tell me what I'm doing wrong?
I might be wrong here but it seems to me that what you want to modify is the
initramfs - is that right? In which case, that is constructed from an image
recipe pointed to by INITRD_IMAGE - by default this is core-image-minimal-
initramfs, but you can point to your own modified image by setting INITRD_IMAGE
within the image recipe (or at the configuration level).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding files to the hddimg
Hello, I'm relatively new to yocto and this is maybe something that is pretty basic but how can I add my own files in the bootimg (.hddimg) using a custom recipes? And I really means the boot image file, not the rootfs image. Thanks, François Gallichand Engineer - Software Group ABB Group Analytical Business (418)877-2944 x268 [ABB logo] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
