[yocto] poky lsb support
HI every body:
I have a package(opensaf) which needs support of lsb init script .So I use
this "DISTRO ?= "poky-lab" in conf/local.conf
And i set IMAGE_INSTALL in my image recipe as follows:
IMAGE_INSTALL = "\
${CORE_IMAGE_BASE_INSTALL} \
packagegroup-core-boot \
bash\
bc \
binutils binutils-symlinks \
coreutils \
cpio \
cronie \
diffutils \
ed \
elfutils \
file \
findutils \
gawk \
grep \
m4 \
ncurses \
libpam \
procps \
psmisc \
sed \
shadow \
tar \
util-linux \
zlib \
lsb \
lsbsetup \
\
dhcp-client \
lsof \
pciutils \
setserial \
strace \
sysstat \
usbutils \
which \
kernel-module-tipc \
libxml2 \
python-shell \
python-xml \
python-subprocess \
eglibc-utils \
tipcutils \
opensaf\
"
I didn't use packagegroup-core-lsb because the flash of my device is very
limited.
When I use the startup script of "opensaf" I always get
"/etc/core-lsb/lsb_start_daemon: line 44 : daemon: command not found
/etc/core-lsb/lsb_log_message: line 16: failure: command not found"
where can I find these commands : "daemon,failure", or which package I need to
include to have these?
PS: my poky branch is danny.
Anybody can help ? thanks very much.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to run script before mount rootfs
Hi, You can have a look at https://wiki.yoctoproject.org/wiki/System_Update. I have used RAUC and u-boot on Rasperry Pi, there is an meta-rauc layer for Yocto. RAUC Dok at https://rauc.readthedocs.io/en/latest/. RAUC have an u-boot example script for loading different rootfs on boot, have a look at there GitHub: https://github.com/rauc/rauc/blob/master/contrib/uboot.sh Best regards Jonas Andersson > 3 juli 2019 kl. 18:59 skrev Szabolcs Báder : > > Hi, > > I created for Raspberry Pi a simple OS-boot-switcher. I change a param from > rootfs, reboot and new OS run. I would like to add to for this flow a > parameter to create ro boot and rootfs. > > I would like to read this parameter at boot and depend on this choose which > OS will load. How could I define this at boot (eg. from cmdline.txt or with a > shell script or load c code ..?). What is the best idea/ way to do that > within Yocto? > > > Thanks in advance, > Szabolcs > -- > ___ > 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] How to patch a recipe .inc file
Hi,
To add some kernel config I have created an extra .cfg file in:
my_recipe/recipes-kernel/linux/linux-raspberrypi/
and add an bb_append file:
recipes-kernel/linux/linux-raspberrypi_%25.bbappend
__
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "file://your_conf.cfg"
__
BR
Jonas
> 8 aug. 2019 kl. 01:02 skrev Greg Wilson-Lindberg :
>
> I'm working with a Yocto Sumo build provided with Qt's boot2qt system. I'm
> trying to enable using initramfs as a step in trying to enable OSTree updates.
>
> In the meta-raspberrypi documentation, section 3.14, it says to add some
> kernel config to the linux-raspberrypi.inc file. I would prefer to keep my
> changes to Yocto layer files in my own tree so I'm trying to figure out how
> to patch the existing file. I've got bitbake finding my patch file, but it
> can't find the file to patch.
>
> Can somebody help me to specify that the file that I'm patching is part of
> the meta-raspberrypi linux recipe?
>
> I'm going to be gone for a week, but I wanted to ask this now so maybe I'll
> have some information when I get back.
>
> Regards,
> Greg Wilson-Lindberg
>
> --
> ___
> 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] nodejs npm qemux86_64
Great!
/Jonas Andersson
> 8 nov. 2019 kl. 10:59 skrev Jean-Marie LEMETAYER
> :
>
> Actually I just update my patchset to use ${nonarch_libdir} instead of
> ${libdir}.
>
> This will be on the next patchset version.
>
> For your information you can check the meta/conf/bitbake.conf file for others
> target filesystem paths.
>
> Best regards,
> Jean-Marie
>
>> On Nov 8, 2019, at 10:46 AM, Jean-Marie LEMETAYER
>> jean-marie.lemeta...@savoirfairelinux.com wrote:
>> Hi Jonas,
>>
>> I am currently refactoring / updating the npm handling in Yocto:
>> http://lists.openembedded.org/pipermail/openembedded-core/2019-October/288352.html
>> http://lists.openembedded.org/pipermail/bitbake-devel/2019-October/020449.html
>>
>> Your point is very interesting, I will take it into account for the next
>> patchset version.
>>
>> Best regards,
>> Jean-Marie
>>
>>> On Nov 7, 2019, at 10:56 PM, Jonas Andersson jonaskganders...@gmail.com
>>> wrote:
>>> Hi,
>>>
>>> I have installation problems for npm recipes.
>>> Using Yocto thud and machine=qemux86_64(wrlinux-x), but as I can see it this
>>> concerns all
>>> use of npm.bbclass for 64-bits system.
>>>
>>> The problem seems to be the use of ${libdir} in npm.bbclass, when 64 bit is
>>> used
>>> this expands to lib64.
>>> npm install --prefix ${D}${prefix} installs to /usr/lib/node_modules which
>>> is
>>> not
>>> in sync with the following mv ${D}${libdir}/node_modules ${D}${libdir}/node.
>>>
>>> I made an quick fix by replacing ${libdir} by ${prefix}/lib/, but as I see
>>> it
>>> nodejs packages never is installed to lib64 in any other system as I can
>>> find
>>> information about.
>>>
>>> So the question is if the use of ${libdir} is bad and the path should
>>> always be
>>> to /lib/?
>>>
>>> Best regards
>>> Jonas
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Regarding build Yocto offline
On Mon, 2018-07-16 at 10:55 +0200, Gunnar Andersson wrote: > [trimmed] > Here is a reference to an earlier discussion - I think it is commonly > recurring question. (Maybe you can propose a change to the docs, to > indicate this near the description of the BB_NO_NETWORK variable?) It seems to already be written in the Wiki you referred to [1]. But I think it might help to put it also in the official manual. - Gunnar [1] https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F -- Gunnar Andersson Development Lead GENIVI Alliance -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] install and use "bitbake -c populate_sdk"
Hi, I have build and boot the image from USB flash disk with the .hddimg created by "bitbake -k core-image-basic" have added ssh server inside and make sure the ethernet works well, then use "bitbake -c populate_sdk core-image-basic" to create the "poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory, my plan is to install the sdk into the target system and compile my kernel module there, but now the problem is: 1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df" command from target said there's 85MB available only, but the sdk .sh installer image is about 300MB, how can I "extend" the target system to use the rest USB disk space? ( it's FAT file system) or how to modify configuration to force build the .hddimg create ~"8GB" file system? 2. after that SDK installed into my target system, can I copy (scp) my own kernel module driver source code into the target system then make/compile and try insmod/debug the .ko there? or should I install the sdk on host system, then copy only the compiled .ko into target system for test/debugging? Eddy ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] install and use "bitbake -c populate_sdk"
I have tried to copy entire "poky/meta-skeleton/recipes-kernel/hello-mod" folder into my target (poky/meta-intel/meta-jasperforest/recipes-kernel) and then add this line MACHINE_EXTRA_RRECOMMENDS += "kernel-module-hello-mod" to conf/local.conf, but can't see hello-ko in the target binary image (core-image-basic) after boot USB from the target hardware, anything else missed ? (yocto 1.3 + jasperforest BSP on x86_64 target) Eddy --- Hi Eddy, I don't think build core-image-sato-sdk is the right approach. Have you looked into following the example of hello-mod under meta-skeleton, to use bitbake to build your kernel module? -Jessica *From:*Lai Eddy [mailto:eddy.lai...@gmail.com] *Sent:* Wednesday, January 30, 2013 7:54 PM *To:* Zhang, Jessica *Cc:* yocto@yoctoproject.org *Subject:* Re: [yocto] install and use "bitbake -c populate_sdk" Thanks Jessica, why I tried to use "-c populate-sdk" is because that I can find "core-image-sato-sdk" but no "core-image-basic-sdk" available, and my hardware is a samll jasperforest x86_64 target with 2 serial port and 1 ethernet port only, no display interface. I'm trying to find if any of following configuration suitable for my kernel module driver develop/debug: 1. with the x86_64 toolchain sdk installed on my x86_64 host , build my kernel module driver, then scp ".ko" binary to target for insmod/debugging, but the problem I have now is the "make" always pointing to /usr/src/3.2.x kernel source path (my host OS's kernel version), but not the linux-yocto target kernel (3.4.x) source/header path (and I don't know where's the proper 3.4.x target kernel header/source files, is it inside tmp/work/...? ) 2.build and run the "core-image-basic" on my target, and install the sdk created with "bitbake core-image-basic -c populate-sdk", but there's no "/usr/src/.." , "/lib/modules/3.4.x-yocto-stand/build" exist trying to build the "core-image-sato-sdk to see if that help for target develop now... Eddy 2013/1/31 Zhang, Jessica <mailto:jessica.zh...@intel.com>> Hi Eddy, The SDK is meant to be used on development host for cross development instead of target. Sounds like you need an sdk image which contains the development tools and needed development library and kernel sources. Please refer to core-image-sato-sdk for how to customize your image to allow your do development work on target. Thanks, Jessica -Original Message- From: yocto-boun...@yoctoproject.org <mailto:yocto-boun...@yoctoproject.org> [mailto:yocto-boun...@yoctoproject.org <mailto:yocto-boun...@yoctoproject.org>] On Behalf Of Eddy Lai GMail Sent: Thursday, January 24, 2013 5:49 AM To: yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> Subject: Re: [yocto] install and use "bitbake -c populate_sdk" Hi, I have build and boot the image from USB flash disk with the .hddimg created by "bitbake -k core-image-basic" have added ssh server inside and make sure the ethernet works well, then use "bitbake -c populate_sdk core-image-basic" to create the "poky_eglibc_xx.sh" under "tmp/deploy/sdk" directory, my plan is to install the sdk into the target system and compile my kernel module there, but now the problem is: 1. even I have 8GB USB flash disk, the .hddimg is 420MB only, "df" command from target said there's 85MB available only, but the sdk .sh installer image is about 300MB, how can I "extend" the target system to use the rest USB disk space? ( it's FAT file system) or how to modify configuration to force build the .hddimg create ~"8GB" file system? 2. after that SDK installed into my target system, can I copy (scp) my own kernel module driver source code into the target system then make/compile and try insmod/debug the .ko there? or should I install the sdk on host system, then copy only the compiled .ko into target system for test/debugging? Eddy ___ yocto mailing list yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
