Re: [yocto] bbappend and placing a file into /tmp on the target

[Bishop, Mark (STRT)]

VOLATILE-BINDS is kinda what I am looking for, but without the dependency of 
systemd

From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Monday, August 13, 2018 5:54 PM
To: Bishop, Mark (STRT)
Cc: Yocto Project
Subject: Re: [yocto] bbappend and placing a file into /tmp on the target

May be look into VOLATILE_BINDS

On Mon, Aug 13, 2018 at 1:12 PM Bishop, Mark (STRT) 
mailto:mbis...@smithsinterconnectinc.com>> 
wrote:
I am trying to expand an existing package (base-passwd) and having it place 
/etc/passwd into /tmp/

I’m failing pretty miserably and am looking for some hints/tips.

Mark Bishop
Sr. Firmware/Software Engineer – Microwave Subsystems

[cid:image001.png@01D281ED.A45F0A90]

4726 Eisenhower Blvd.
Tampa, FL 33634
USA


T  +1 813 901 7293

mbis...@smithsinterconnectinc.com<mailto:mbis...@smithsinterconnectinc.com>

smithsinterconnect.com<http://www.smithsinterconnect.com/>

TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!




This e-mail contains proprietary information some or all of which may be 
legally privileged. It is intended for the recipient only. If an addressing or 
transmission error has misdirected this e-mail, please notify the authority by 
replying to this e-mail. If you are not the intended recipient you must not 
use, disclose, distribute, copy, print, or rely on this e-mail. In addition, 
information contained in or attached to this e-mail may be subject to either 22 
C.F.R. Parts 120?130, or 15 C.F.R. Parts 730-774. These regulations prohibit 
the release or disclosure of certain information contained herein to anyone who 
is not a U.S. citizen or permanent resident alien, without a license first 
having been issued. Failure to observe such requirements is a violation of U.S. 
law that carries serious penalties.   ­­
--
___
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

[yocto] bbappend and placing a file into /tmp on the target

[Bishop, Mark (STRT)]

I am trying to expand an existing package (base-passwd) and having it place 
/etc/passwd into /tmp/

I'm failing pretty miserably and am looking for some hints/tips.

Mark Bishop
Sr. Firmware/Software Engineer - Microwave Subsystems

[cid:image001.png@01D281ED.A45F0A90]

4726 Eisenhower Blvd.
Tampa, FL 33634
USA


T  +1 813 901 7293

mbis...@smithsinterconnectinc.com

smithsinterconnect.com

TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] changing the apache2 conf (meta-webserver)

[Bishop, Mark (STRT)]

I want to change the ErrorLog entries.  It's a common thing to do but I need 
help in how to do that in Yocto.

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Khem Raj
Sent: Monday, February 05, 2018 3:07 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] changing the apache2 conf (meta-webserver)

On 2/5/18 11:45 AM, Bishop, Mark (STRT) wrote:
> Let me start with that I'm new to Yocto.
> 
>  
> 
> I've been able to get apache2 onto my zynq board but I need to change 
> the config.  I'm using a read-only rootfs and apache won't start 
> because it wants to write to a log file.  I know what I need to change 
> in the apache config but I have no idea how to do that in Yocto.  
> Could anyone walk me through it and if I am in the wrong spot, my apologies.

you might need to provide some r/w storage here it seems. Either you can 
symlink back /tmp to /var/log ( a hack ) or provide a  proper storage thats 
persistent and mount it on /var/log or whereever it is expecting to write.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] changing the apache2 conf (meta-webserver)

[Bishop, Mark (STRT)]

Let me start with that I'm new to Yocto.



I've been able to get apache2 onto my zynq board but I need to change the 
config.  I'm using a read-only rootfs and apache won't start because it wants 
to write to a log file.  I know what I need to change in the apache config but 
I have no idea how to do that in Yocto.  Could anyone walk me through it and if 
I am in the wrong spot, my apologies.




Mark Bishop
Sr. Firmware/Software Engineer - Microwave Subsystems

[cid:image001.png@01D281ED.A45F0A90]

4726 Eisenhower Blvd.
Tampa, FL 33634
USA


T  +1 813 901 7293

mbis...@smithsinterconnectinc.com

smithsinterconnect.com

TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Change initscript level

[Bishop, Mark (STRT)]

I am just trying to change modutils.sh to run from /etc/rcS.d/S05modutils.sh to 
/etc/rcS.d/S15modutils.sh

I can't figure this out.  I have modified the 
yocto/source/arm/layers/core/meta/recipes-kernel/modutils-initscripts.bb

From: INITSCRIPT_PARAMS = "start 05 S ."
To: INITSCRIPT_PARAMS = "start 10 S ."

And I still only have S05modutils.sh

The pkg_postinst_modutils-initscripts still has "start 05 S ." in 
build/tmp/work/cortexa9hf-neon-xilinx-linux-gnueabi/modutils-initscripts/1.0-r7/pkgdata/runtime/modutils-initscripts

It's quite apparent that I don't know what I'm doing here and I could use some 
sage advice on how to move these startup levels around.

Thank you.

Mark Bishop
Sr. Firmware/Software Engineer - Microwave Subsystems

[cid:image001.png@01D281ED.A45F0A90]

4726 Eisenhower Blvd.
Tampa, FL 33634
USA


T  +1 813 901 7293

mbis...@smithsinterconnectinc.com

smithsinterconnect.com

TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] do_kernel_checkout() not using the correct directory

[Bishop, Mark (STRT)]

I changed the code in  arm/layers/core/meta/classes/kernel-yocto.bbclass

From:
.
else
    # case: we have no git repository at all. 
# To support low bandwidth options for building the kernel, 
we'll just 
# convert the tree to a git repo and let the rest of the 
process work unchanged

    # if ${S} hasn't been set to the proper subdirectory a default 
of "linux" is 
# used, but we can't initialize that empty directory. So check 
it and throw a
    # clear error

    cd ${S}
    if [ ! -f "Makefile" ]; then
..

To:
else
# case: we have no git repository at all. 
# To support low bandwidth options for building the kernel, 
we'll just 
# convert the tree to a git repo and let the rest of the 
process work unchanged

# if ${S} hasn't been set to the proper subdirectory a default 
of "linux" is 
# used, but we can't initialize that empty directory. So check 
it and throw a
# clear error

if [ -d "${WORKDIR}/trunk/" ]; then
source_workdir="${WORKDIR}/trunk"
if [ "${source_dir}" != "${source_workdir}" ]; then
rm -rf ${S}
mv ${WORKDIR}/trunk ${S}
fi
fi

cd ${S}
if [ ! -f "Makefile" ]; then

And everything is working but it seems that this would be the wrong way to do 
this as this is me editing a base class file.  



From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Bishop, Mark (STRT)
Sent: Thursday, November 02, 2017 1:48 PM
To: yocto@yoctoproject.org
Subject: [yocto] do_kernel_checkout() not using the correct directory

I am trying to compile a kernel located in SVN.

I get this error message:
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: S 
/tmp/stride/work-shared/plnx_arm/kernel-source is not set to the linux source 
directory. Check 
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: the recipe 
and set S to the proper extracted subdirectory
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: Function 
failed: do_kernel_checkout (log file is located at 
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928)
ERROR: Logfile of failure stored in: 
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928
ERROR: Task 
(/opt/pkg/petalinux/2017.2/components/yocto/source/arm/layers/meta-xilinx/recipes-kernel/linux/linux-xlnx_4.9.bb:do_kernel_checkout)
 failed with exit code '1'

And my kernel gets downloaded to:
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/trunk
But Yocto is looking for it in /tmp/stride/work-shared/plnx_arm/kernel-source
Which is why it is failing in kernel-yocto.bbclass when I try and compile a 
kernel located in SVN.

If it is a git repo it gets copied into 
/tmp/stride/work-shared/plnx_arm/kernel-source and things work nicely.


do_kernel_checkout() {
...
if [ -d "${WORKDIR}/git/" ]; then
   # case: git repository
    # if S is WORKDIR/git, then we shouldn't be moving or deleting 
the tree.
    if [ "${source_dir}" != "${source_workdir}" ]; then
    if [ -d "${source_workdir}/.git" ]; then
    # regular git repository with .git
    rm -rf ${S}
    mv ${WORKDIR}/git ${S}
    else
    # create source for bare cloned git repository
    git clone ${WORKDIR}/git ${S}
    rm -rf ${WORKDIR}/git
    fi
    fi
    cd ${S}
else
    # case: we have no git repository at all. 
# To support low bandwidth options for building the kernel, 
we'll just 
# convert the tree to a git repo and let the rest of the 
process work unchanged

    # if ${S} hasn't been set to the proper subdirectory a default 
of "linux" is 
# used, but we can't initialize that empty directory. So check 
it and throw a
    # clear error

    cd ${S}
    if [ ! -f "Makefile" ]; then
    bberror "S ${S} is not set to the linux source 
directory. Check "
    bbfatal "the recipe and set S to the proper extracted 
subdirectory"
    fi
.

[yocto] do_kernel_checkout() not using the correct directory

[Bishop, Mark (STRT)]

I am trying to compile a kernel located in SVN.

I get this error message:
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: S 
/tmp/stride/work-shared/plnx_arm/kernel-source is not set to the linux source 
directory. Check
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: the recipe 
and set S to the proper extracted subdirectory
ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: Function 
failed: do_kernel_checkout (log file is located at 
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928)
ERROR: Logfile of failure stored in: 
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/temp/log.do_kernel_checkout.34928
ERROR: Task 
(/opt/pkg/petalinux/2017.2/components/yocto/source/arm/layers/meta-xilinx/recipes-kernel/linux/linux-xlnx_4.9.bb:do_kernel_checkout)
 failed with exit code '1'

And my kernel gets downloaded to:
/tmp/stride/work/plnx_arm-xilinx-linux-gnueabi/linux-xlnx/4.9-xilinx-v2017.2+git20-r0/trunk
But Yocto is looking for it in /tmp/stride/work-shared/plnx_arm/kernel-source
Which is why it is failing in kernel-yocto.bbclass when I try and compile a 
kernel located in SVN.

If it is a git repo it gets copied into 
/tmp/stride/work-shared/plnx_arm/kernel-source and things work nicely.


do_kernel_checkout() {
...
if [ -d "${WORKDIR}/git/" ]; then
# case: git repository
# if S is WORKDIR/git, then we shouldn't be moving or deleting 
the tree.
if [ "${source_dir}" != "${source_workdir}" ]; then
if [ -d "${source_workdir}/.git" ]; then
# regular git repository with .git
rm -rf ${S}
mv ${WORKDIR}/git ${S}
else
# create source for bare cloned git repository
git clone ${WORKDIR}/git ${S}
rm -rf ${WORKDIR}/git
fi
fi
cd ${S}
else
# case: we have no git repository at all.
# To support low bandwidth options for building the kernel, 
we'll just
# convert the tree to a git repo and let the rest of the 
process work unchanged

# if ${S} hasn't been set to the proper subdirectory a default 
of "linux" is
# used, but we can't initialize that empty directory. So check 
it and throw a
# clear error

cd ${S}
if [ ! -f "Makefile" ]; then
bberror "S ${S} is not set to the linux source 
directory. Check "
bbfatal "the recipe and set S to the proper extracted 
subdirectory"
fi
..

${S} is set to /tmp/stride/work-shared/plnx_arm/kernel-source when I need one 
of the two things to happen:

A) ${S} set to  ${WORKDIR}/trunk OR

B)  ${WORKDIR}/trunk copied to ${S}/

I could modify that file directly on my machine and move on, but is there a way 
I can create an .bbappend or something that will change ${S}

I'm pretty new to Yocto and I'd like to have a solution that resides in my 
project folder instead of having to modify Yocto files so that when I do tool 
installs on new development machines I can just checkout my project data and 
have it work.  I'm using Petalinux, so the process would be install that, then 
checkout the project and then build it, with the correct ${S} directory flowing 
into kernel-yocto.bbclass:do_kernel_checkout()

I'm new Yocto but I've been reading a ton and am looking for some advice.





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto