Re: [yocto] recipe to clean up files from rootfs
On Wed, Dec 13, 2017 at 11:06 PM, Sherif Omran
wrote:
> Here is my recipe, it runs suceeds but does not delete the files
>
> mypostprocesfunction() {
> rm -r ${IMAGE_ROOTFS}/etc/init.d/psplash.sh
> rm -r ${IMAGE_ROOTFS}/usr/bin/psplash*
> }
>
> ROOTFS_POSTPROCESS_COMMAND += "mypostprocessfunction; "
>
I think you are fundamentally misunderstanding how recipes work. At a
very high level, recipes are used to compile sources into installable
packages (e.g. ipk or rpm files) and then (as a separate step) an
image recipe creates the rootfs by unpacking a set of installable
packages.
One recipe can depend on the output of another (e.g. an image recipe
depends on the installable packages created by other recipes) but each
recipe has it's own execution environment. You can't expect to write a
recipe which changes the behaviour of another recipe, so writing a new
recipe to remove some files from the rootfs created by the image
recipe is fundamentally wrong. It's never going to work, even if you
fix every typo.
As suggested already, the normal and recommended way to remove files
from the rootfs is:
1) Remove the package which provides the file(s) from the image you
are building (ie don't install the files in the rootfs at all).
If the file(s) you want to remove don't match the granularity of the
installable packages (ie you want to keep some files provided by a
package but remove others) then you have two basic options:
2) Spilt the installable package into multiple smaller installable
packages (ie modify the packaging rules in the recipe which creates
the installable package).
3) Postprocess the rootfs. For that to work, you need to add the
postprocessing function ** TO THE IMAGE RECIPE **.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] recipe to clean up files from rootfs
Hi Sherif,
On 2017-12-14 08:06, Sherif Omran wrote:
Here is my recipe, it runs suceeds but does not delete the files
mypostprocesfunction() {
rm -r ${IMAGE_ROOTFS}/etc/init.d/psplash.sh
rm -r ${IMAGE_ROOTFS}/usr/bin/psplash*
}
ROOTFS_POSTPROCESS_COMMAND += "mypostprocessfunction; "
Unless you did a copy-paste error, there's a typo in the function name:
mypostprocesfunction
mypostprocessfunction
// Martin
On Wed, Dec 13, 2017 at 2:03 PM, Mike Looijmans > wrote:
${D} won't work here, grep on ROOTFS_POSTPROCESS_COMMAND for recipes
that get it right.
And, much much much better would be to just not install psplash into
your image!
On 13-12-17 09:10, Sherif Omran wrote:
here is my recipe, the aim was to remove some files from the
init.d folder and tweek before creating the image
#
# This file was derived from the 'Hello World!' example recipe
in the
# Yocto Project Development Manual.
#
SUMMARY = "This recipe removes any missing files from the
filesystem before finalinzing it"
SECTION = "base"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
#SRC_URI = "file://*"
S = "${WORKDIR}"
BB_STRICT_CHECKSUM ="0"
ALLOW_EMPTY_${PN}="1"
#IMAGE_INSTALL = "packagegroup-core-boot
packagegroup-base-extended ${CORE_IMAGE_EXTRA_INSTALL}"
#IMAGE_INSTALL = "${CORE_IMAGE}"
#inherit core-image
my_postprocess_function() {
rm -r ${D}${bindir}/init.d/psplash.sh
}
ROOTFS_POSTPROCESS_COMMAND += "my_postprocess_function; "
On Wed, Dec 13, 2017 at 7:22 AM, Mike Looijmans
mailto:mike.looijm...@topic.nl>
>> wrote:
Well, start by sharing yours first.
Be careful when naming your shell routine, sometimes OE
considers parts
behind the underscore as overrides and then it cannot find it.
On 13-12-17 07:14, Sherif Omran wrote:
hi Mike,
i could not get it to work, if you have a recipe that
works, please
share it. ROOTFS_POSTPROCESS_COMMAND seems to be buggy.
thank you
On Tue, Dec 12, 2017 at 1:58 PM, Mike Looijmans
mailto:mike.looijm...@topic.nl> >
>
>>
Website: www.topicproducts.com
Please consider the environment before printing
this e-mail
--
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mai
Re: [yocto] recipe to clean up files from rootfs
Here is my recipe, it runs suceeds but does not delete the files
mypostprocesfunction() {
rm -r ${IMAGE_ROOTFS}/etc/init.d/psplash.sh
rm -r ${IMAGE_ROOTFS}/usr/bin/psplash*
}
ROOTFS_POSTPROCESS_COMMAND += "mypostprocessfunction; "
On Wed, Dec 13, 2017 at 2:03 PM, Mike Looijmans
wrote:
> ${D} won't work here, grep on ROOTFS_POSTPROCESS_COMMAND for recipes that
> get it right.
>
> And, much much much better would be to just not install psplash into your
> image!
>
> On 13-12-17 09:10, Sherif Omran wrote:
>
>> here is my recipe, the aim was to remove some files from the init.d
>> folder and tweek before creating the image
>>
>> #
>> # This file was derived from the 'Hello World!' example recipe in the
>> # Yocto Project Development Manual.
>> #
>>
>> SUMMARY = "This recipe removes any missing files from the filesystem
>> before finalinzing it"
>> SECTION = "base"
>> LICENSE = "MIT"
>> LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/
>> MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>>
>> #SRC_URI = "file://*"
>>
>> S = "${WORKDIR}"
>> BB_STRICT_CHECKSUM ="0"
>> ALLOW_EMPTY_${PN}="1"
>>
>>
>> #IMAGE_INSTALL = "packagegroup-core-boot packagegroup-base-extended
>> ${CORE_IMAGE_EXTRA_INSTALL}"
>> #IMAGE_INSTALL = "${CORE_IMAGE}"
>>
>> #inherit core-image
>>
>> my_postprocess_function() {
>> rm -r ${D}${bindir}/init.d/psplash.sh
>> }
>>
>> ROOTFS_POSTPROCESS_COMMAND += "my_postprocess_function; "
>>
>> On Wed, Dec 13, 2017 at 7:22 AM, Mike Looijmans > > wrote:
>>
>> Well, start by sharing yours first.
>>
>> Be careful when naming your shell routine, sometimes OE considers
>> parts
>> behind the underscore as overrides and then it cannot find it.
>>
>>
>> On 13-12-17 07:14, Sherif Omran wrote:
>>
>> hi Mike,
>> i could not get it to work, if you have a recipe that works,
>> please
>> share it. ROOTFS_POSTPROCESS_COMMAND seems to be buggy.
>>
>> thank you
>>
>>
>>
>> On Tue, Dec 12, 2017 at 1:58 PM, Mike Looijmans
>> mailto:mike.looijm...@topic.nl>
>> >>
>> wrote:
>>
>> On 11-12-17 15:18, Sherif Omran wrote:
>>
>> i want to create a recipe to clean some files from the
>> rootfile
>> system, but i don't know how to let this recipe run the
>> last one
>> before building the rootfile system.
>>
>>
>> You can use ROOTFS_POSTPROCESS_COMMAND in your image recipe
>> to do
>> some
>> last-minute filesystem cleanup.
>>
>> However, in most cases it's much better to determine what
>> recipe
>> puts the
>> files there and modify the recipe or remove the package. It
>> would
>> help a
>> lot if you would reveal what files you want to remove and
>> why.
>>
>>
>> Kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>> TOPIC Products
>> Materiaalweg 4, NL-5681 RJ Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: +31 (0) 499 33 69 79
>>
>>
>> E-mail: mike.looijm...@topicproducts.com
>>
>> >
>> >
>> Website: www.topicproducts.com > >
>>
>>
>> Please consider the environment before printing this e-mail
>>
>>
>>
>> --
>>
>>
>> Kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>> TOPIC Products
>> Materiaalweg 4, NL-5681 RJ Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: +31 (0) 499 33 69 79 > 3%2069%2079>
>> E-mail: mike.looijm...@topicproducts.com
>>
>> Website: www.topicproducts.com
>>
>> Please consider the environment before printing this e-mail
>>
>>
>>
>>
>>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Products
> Materiaalweg 4, NL-5681 RJ Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijm...@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
> ___
>
>>
>> yocto mailing list
>> yocto@yoctoproject.org
>> >
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> > >
>>
>>
>>
>>
>>
>
--
___
yocto mailing
Re: [yocto] Permission denied while building rocko on Debian 8
Hi list
See below
On 11/12/17 15:22, Mircea Gliga wrote:
On 11/12/17 15:06, Paul Barker wrote:
On Mon, Dec 11, 2017 at 12:43 PM, Mircea Gliga
wrote:
So I went further and I tested in a VM running Debian 9 - there it
works:
It looks like I get a Permission denied while building rocko only on
Debian
8, *not* on Debian 9.
Debian 8 is listed as supported on Yocto Project Reference Manual
here:
http://www.yoctoproject.org/docs/2.4/ref-manual/ref-manual.html#detailed-supported-distros
Can somebody confirm this behavior ? It's a straight forward test:
$ git clone -b rocko git://git.yoctoproject.org/poky.git
$ source poky/oe-init-build-env
$ bitbake core-image-minimal
This looks like a weird permission issue rather than something
Yocto-related. How are you running your Debian 8 system? Is it bare
metal, VM, container, some hosting providers VPS, etc?
Indeed, the problem on the Debian 8 machine was that the following
command was run sometime in the past - we needed a python service to
listen on a privileged port:
$ sudo setcap 'cap_net_bind_service=+ep' '/usr/bin/python3.5'
Doing a setcap -r /usr/bin/python3.5 fixes the problem.
So it has nothing to do with Yocto!
Thanks for support.
Debian 8 is running on a real system, no VM etc.
I used netinstall with no desktop environment and without all the
blows and whistles and added just what I needed, when I needed it.
This machine was used for the last 1,5 years or so for developing on
Krogoth.
I was able to reproduce the problem on a second box, real machine,
running Debian 8
Meanwhile I tried building rocko on another real machine, running
Debian 9 - it works. ( in the prev email I tested in a Debian 9 VM)
Thanks
PS I've updated the thread subject to better reflect the problem.
Thanks
On 11/12/17 09:58, Mircea Gliga wrote:
Hello,
I have a working krogoth build - I build images etc, everything is
fine.
Then I wanted to try a rocko build, I installed the needed host
packages:
http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages
Then sourced env and bitbake core-image-minimal.
So no extra layers involved, just poky.
I get errors like this:
ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
Build
of do_fetch failed
ERROR: gnu-config-native-20150728+gitAUTOINC+b576fa87c1-r0 do_fetch:
Traceback (most recent call last):
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
line 644, in exec_task
return _exec_task(fn, task, d, quieterr)
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/build.py",
line 618, in _exec_task
event.fire(TaskSucceeded(task, logfn, localdata), localdata)
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 222, in fire
fire_class_handlers(event, d)
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 134, in fire_class_handlers
execute_handler(name, handler, event, d)
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/bitbake/lib/bb/event.py",
line 106, in execute_handler
ret = handler(event)
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 166, in run_buildstats
write_task_data("passed", os.path.join(taskdir, e.task), e, d)
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 90, in write_task_data
cpu, iostats, resources, childres =
get_process_cputime(os.getpid())
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 29, in get_process_cputime
with open("/proc/%d/io" % pid, "r") as f:
PermissionError: [Errno 13] Permission denied: '/proc/1530/io'
ERROR: Task
(virtual:native:/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_fetch)
failed with exit code '1'
ERROR: autoconf-native-2.69-r11 do_fetch: Execution of event handler
'run_buildstats' failed
Traceback (most recent call last):
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 166, in run_buildstats(e=):
elif isinstance(e, bb.build.TaskSucceeded):
> write_task_data("passed", os.path.join(taskdir,
e.task), e, d)
if e.task == "do_rootfs":
File
"/media/mircea/ExtLinux/Adventure/repository/rocko/poky/meta/classes/buildstats.bbclass",
line 90, in write_task_data(status='passed',
logfile='/media/mircea/ExtLinux/Adventure/repository/rocko/build/tmp/buildstats/20171211074610/autoconf-native-2.69-r11/do_fetch',
e=,
d=):
f.write(d.expand("Elapsed time: %0.2f seconds\n" %
elapsedtime))
> cpu, iostats, resources, childres =
get_process_cputime(os.getpid())
if cpu:
File
"/media/mircea/ExtLinux/Adventure/repository/rock
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
> I'm seeing the same build errors in linux-raspberrypi with various
versions of Gentoo and
> Ubuntu (mostly tested with 14.04 and 16.04), I doubt that this issue is
specific for Fedora 27.
Divide and Conquer. ;-)
Good. New details emerged. So one problem off the potential problem list.
Zoran
On Thu, Dec 14, 2017 at 6:47 AM, Martin Jansa
wrote:
> I'm seeing the same build errors in linux-raspberrypi with various
> versions of Gentoo and Ubuntu (mostly tested with 14.04 and 16.04), I doubt
> that this issue is specific for Fedora 27.
>
> On Thu, Dec 14, 2017 at 2:31 PM, Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
>
>> > Also is worth noting that I'm running Fedora 27 which wasn't tested...
>>
>> You should start from here your investigation, since you are on not
>> tested YOCTO host distribution. And Fedoras are
>> different from release to release, certainly!
>>
>> So either you should downgrade your fedora 27 to 26 (which I doubt it is
>> possible), better to build brand new Fedora 26
>> using exactly the same packages.
>>
>> Here is a bit of help: to port all the packages to fresh installed Fedora
>> 26, use the following command to retrieve
>> packages from Fedora 27: rpm -qa --qf "%{name}.%{arch}\n" >
>> packages-list.txt
>>
>> Zoran
>>
>> On Mon, Dec 11, 2017 at 12:34 PM, Daniel. wrote:
>>
>>> I can anticipate some info for you. I'm on version 2.4 Rocko. Building
>>> rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm
>>> running Fedora 27 which wasn't tested...
>>>
>>> I'll try to get the full log tonight and let you know
>>>
>>> Regards
>>>
>>> On Dec 11, 2017 9:26 AM, "Daniel." wrote:
>>>
Yeah but I got to face the error again, maybe tonight when I get home :)
On Dec 11, 2017 9:17 AM, "Paul Barker" wrote:
> On Sun, Dec 10, 2017 at 5:14 PM, Daniel.
> wrote:
> > Hi everybody,
> >
> > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing
> the
> > build for the first time and faced an error at
> > linux-raspberrypi:do_kernel_configme. I found that
> .kernel-meta/configs
> > folder was missing, so I fired a devshell and created it. After that
> > everything works as expected and linux-raspberrypi build fines.
> >
> > The solution I got is palliative, what would be the real solution
> and what
> > is this .kernel-meta folder? I had never seem this folder before.
>
> I have seen this issue occasionally when the do_kernel_configme task
> is re-executed. A "bitbake virtual/kernel -c clean" has always
> resolved this for me, allowing the next build to succeed. It doesn't
> occur on my autobuild systems though so I figure it's an edge case I'm
> hitting when building locally as I'm hacking around on recipes.
>
> I've never seen this on the first build of the kernel though.
>
> Which version of Yocto are you using? Could you send us the build
> configuration summary and the full error messages printed by bitbake?
>
> Thanks,
>
> --
> Paul Barker
> Togán Labs Ltd
>
>>> --
>>> ___
>>> 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
I'm seeing the same build errors in linux-raspberrypi with various versions
of Gentoo and Ubuntu (mostly tested with 14.04 and 16.04), I doubt that
this issue is specific for Fedora 27.
On Thu, Dec 14, 2017 at 2:31 PM, Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> > Also is worth noting that I'm running Fedora 27 which wasn't tested...
>
> You should start from here your investigation, since you are on not tested
> YOCTO host distribution. And Fedoras are
> different from release to release, certainly!
>
> So either you should downgrade your fedora 27 to 26 (which I doubt it is
> possible), better to build brand new Fedora 26
> using exactly the same packages.
>
> Here is a bit of help: to port all the packages to fresh installed Fedora
> 26, use the following command to retrieve
> packages from Fedora 27: rpm -qa --qf "%{name}.%{arch}\n" >
> packages-list.txt
>
> Zoran
>
> On Mon, Dec 11, 2017 at 12:34 PM, Daniel. wrote:
>
>> I can anticipate some info for you. I'm on version 2.4 Rocko. Building
>> rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm
>> running Fedora 27 which wasn't tested...
>>
>> I'll try to get the full log tonight and let you know
>>
>> Regards
>>
>> On Dec 11, 2017 9:26 AM, "Daniel." wrote:
>>
>>> Yeah but I got to face the error again, maybe tonight when I get home :)
>>>
>>> On Dec 11, 2017 9:17 AM, "Paul Barker" wrote:
>>>
On Sun, Dec 10, 2017 at 5:14 PM, Daniel. wrote:
> Hi everybody,
>
> I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing
the
> build for the first time and faced an error at
> linux-raspberrypi:do_kernel_configme. I found that
.kernel-meta/configs
> folder was missing, so I fired a devshell and created it. After that
> everything works as expected and linux-raspberrypi build fines.
>
> The solution I got is palliative, what would be the real solution and
what
> is this .kernel-meta folder? I had never seem this folder before.
I have seen this issue occasionally when the do_kernel_configme task
is re-executed. A "bitbake virtual/kernel -c clean" has always
resolved this for me, allowing the next build to succeed. It doesn't
occur on my autobuild systems though so I figure it's an edge case I'm
hitting when building locally as I'm hacking around on recipes.
I've never seen this on the first build of the kernel though.
Which version of Yocto are you using? Could you send us the build
configuration summary and the full error messages printed by bitbake?
Thanks,
--
Paul Barker
Togán Labs Ltd
>>>
>> --
>> ___
>> 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
> Also is worth noting that I'm running Fedora 27 which wasn't tested...
You should start from here your investigation, since you are on not tested
YOCTO host distribution. And Fedoras are
different from release to release, certainly!
So either you should downgrade your fedora 27 to 26 (which I doubt it is
possible), better to build brand new Fedora 26
using exactly the same packages.
Here is a bit of help: to port all the packages to fresh installed Fedora
26, use the following command to retrieve
packages from Fedora 27: rpm -qa --qf "%{name}.%{arch}\n" >
packages-list.txt
Zoran
On Mon, Dec 11, 2017 at 12:34 PM, Daniel. wrote:
> I can anticipate some info for you. I'm on version 2.4 Rocko. Building
> rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm
> running Fedora 27 which wasn't tested...
>
> I'll try to get the full log tonight and let you know
>
> Regards
>
> On Dec 11, 2017 9:26 AM, "Daniel." wrote:
>
>> Yeah but I got to face the error again, maybe tonight when I get home :)
>>
>> On Dec 11, 2017 9:17 AM, "Paul Barker" wrote:
>>
>>> On Sun, Dec 10, 2017 at 5:14 PM, Daniel. wrote:
>>> > Hi everybody,
>>> >
>>> > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing the
>>> > build for the first time and faced an error at
>>> > linux-raspberrypi:do_kernel_configme. I found that
>>> .kernel-meta/configs
>>> > folder was missing, so I fired a devshell and created it. After that
>>> > everything works as expected and linux-raspberrypi build fines.
>>> >
>>> > The solution I got is palliative, what would be the real solution and
>>> what
>>> > is this .kernel-meta folder? I had never seem this folder before.
>>>
>>> I have seen this issue occasionally when the do_kernel_configme task
>>> is re-executed. A "bitbake virtual/kernel -c clean" has always
>>> resolved this for me, allowing the next build to succeed. It doesn't
>>> occur on my autobuild systems though so I figure it's an edge case I'm
>>> hitting when building locally as I'm hacking around on recipes.
>>>
>>> I've never seen this on the first build of the kernel though.
>>>
>>> Which version of Yocto are you using? Could you send us the build
>>> configuration summary and the full error messages printed by bitbake?
>>>
>>> Thanks,
>>>
>>> --
>>> Paul Barker
>>> Togán Labs Ltd
>>>
>>
> --
> ___
> 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] .kernel-meta/configs folder missing make linux-raspberrypi to fail
PS: I just notice now that I have meta-python duplicated at bblayers.conf, 2017-12-14 0:27 GMT-02:00 Daniel. : > Okay, sorry for the late reply! > > I could reproduce the same error again, I just cleanall and then build > linux-raspberrypi again. Let's go to the logs: > > The whole output: https://pastebin.com/zHLpPf5V > My config: https://pastebin.com/mKJb2tyJ > Configured layers: https://pastebin.com/7UakkhHJ > https://pastebin.com/xKRd8rDr > The layers commits: https://pastebin.com/9pJCrdh4 > > I'll let it stay in this state, so if you need any other information just > let me know and I gather it for you. Again, I'm on fedora 27, kernel > 4.14.3-300.fc27.x86_64, i3, 8GB ram. I think this is it. > > Regards! > > > 2017-12-11 9:34 GMT-02:00 Daniel. : > >> I can anticipate some info for you. I'm on version 2.4 Rocko. Building >> rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm >> running Fedora 27 which wasn't tested... >> >> I'll try to get the full log tonight and let you know >> >> Regards >> >> On Dec 11, 2017 9:26 AM, "Daniel." wrote: >> >>> Yeah but I got to face the error again, maybe tonight when I get home :) >>> >>> On Dec 11, 2017 9:17 AM, "Paul Barker" wrote: >>> On Sun, Dec 10, 2017 at 5:14 PM, Daniel. wrote: > Hi everybody, > > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing the > build for the first time and faced an error at > linux-raspberrypi:do_kernel_configme. I found that .kernel-meta/configs > folder was missing, so I fired a devshell and created it. After that > everything works as expected and linux-raspberrypi build fines. > > The solution I got is palliative, what would be the real solution and what > is this .kernel-meta folder? I had never seem this folder before. I have seen this issue occasionally when the do_kernel_configme task is re-executed. A "bitbake virtual/kernel -c clean" has always resolved this for me, allowing the next build to succeed. It doesn't occur on my autobuild systems though so I figure it's an edge case I'm hitting when building locally as I'm hacking around on recipes. I've never seen this on the first build of the kernel though. Which version of Yocto are you using? Could you send us the build configuration summary and the full error messages printed by bitbake? Thanks, -- Paul Barker Togán Labs Ltd >>> > > > -- > “If you're going to try, go all the way. Otherwise, don't even start. ..." > Charles Bukowski > -- “If you're going to try, go all the way. Otherwise, don't even start. ..." Charles Bukowski -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
Okay, sorry for the late reply! I could reproduce the same error again, I just cleanall and then build linux-raspberrypi again. Let's go to the logs: The whole output: https://pastebin.com/zHLpPf5V My config: https://pastebin.com/mKJb2tyJ Configured layers: https://pastebin.com/7UakkhHJ https://pastebin.com/xKRd8rDr The layers commits: https://pastebin.com/9pJCrdh4 I'll let it stay in this state, so if you need any other information just let me know and I gather it for you. Again, I'm on fedora 27, kernel 4.14.3-300.fc27.x86_64, i3, 8GB ram. I think this is it. Regards! 2017-12-11 9:34 GMT-02:00 Daniel. : > I can anticipate some info for you. I'm on version 2.4 Rocko. Building > rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm > running Fedora 27 which wasn't tested... > > I'll try to get the full log tonight and let you know > > Regards > > On Dec 11, 2017 9:26 AM, "Daniel." wrote: > >> Yeah but I got to face the error again, maybe tonight when I get home :) >> >> On Dec 11, 2017 9:17 AM, "Paul Barker" wrote: >> >>> On Sun, Dec 10, 2017 at 5:14 PM, Daniel. wrote: >>> > Hi everybody, >>> > >>> > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing the >>> > build for the first time and faced an error at >>> > linux-raspberrypi:do_kernel_configme. I found that >>> .kernel-meta/configs >>> > folder was missing, so I fired a devshell and created it. After that >>> > everything works as expected and linux-raspberrypi build fines. >>> > >>> > The solution I got is palliative, what would be the real solution and >>> what >>> > is this .kernel-meta folder? I had never seem this folder before. >>> >>> I have seen this issue occasionally when the do_kernel_configme task >>> is re-executed. A "bitbake virtual/kernel -c clean" has always >>> resolved this for me, allowing the next build to succeed. It doesn't >>> occur on my autobuild systems though so I figure it's an edge case I'm >>> hitting when building locally as I'm hacking around on recipes. >>> >>> I've never seen this on the first build of the kernel though. >>> >>> Which version of Yocto are you using? Could you send us the build >>> configuration summary and the full error messages printed by bitbake? >>> >>> Thanks, >>> >>> -- >>> Paul Barker >>> Togán Labs Ltd >>> >> -- “If you're going to try, go all the way. Otherwise, don't even start. ..." Charles Bukowski -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified
On 12/13/2017 09:18 PM, Alexander Kanavin wrote: On 12/13/2017 03:16 AM, Robert Yang wrote: How about simply issuing 'git revert' after a build has failed? That's easier to implement than rearranging the order of commits, and the commit message can include a link to the build failure logs. Sounds reasonable to me, I will update the patch. Wait until I publish my devtool port, then if you could rebase on that, that'd be great! Got it, thanks. // Robert Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] linux kernel rt
hey guys, any body tried the real time kernel? I get an error, it is snot in the compatibility list. can we skip it? thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] CROPS status?
Hi, I recently discovered the CROPS project at https://github.com/crops/crops. It looks like a great idea, but I see it hasn't had a commit since June 23, 2016. Is the project still active? Thanks, Martin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] recipe to clean up files from rootfs
${D} won't work here, grep on ROOTFS_POSTPROCESS_COMMAND for recipes that get
it right.
And, much much much better would be to just not install psplash into your image!
On 13-12-17 09:10, Sherif Omran wrote:
here is my recipe, the aim was to remove some files from the init.d folder and
tweek before creating the image
#
# This file was derived from the 'Hello World!' example recipe in the
# Yocto Project Development Manual.
#
SUMMARY = "This recipe removes any missing files from the filesystem before
finalinzing it"
SECTION = "base"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
#SRC_URI = "file://*"
S = "${WORKDIR}"
BB_STRICT_CHECKSUM ="0"
ALLOW_EMPTY_${PN}="1"
#IMAGE_INSTALL = "packagegroup-core-boot packagegroup-base-extended
${CORE_IMAGE_EXTRA_INSTALL}"
#IMAGE_INSTALL = "${CORE_IMAGE}"
#inherit core-image
my_postprocess_function() {
rm -r ${D}${bindir}/init.d/psplash.sh
}
ROOTFS_POSTPROCESS_COMMAND += "my_postprocess_function; "
On Wed, Dec 13, 2017 at 7:22 AM, Mike Looijmans > wrote:
Well, start by sharing yours first.
Be careful when naming your shell routine, sometimes OE considers parts
behind the underscore as overrides and then it cannot find it.
On 13-12-17 07:14, Sherif Omran wrote:
hi Mike,
i could not get it to work, if you have a recipe that works, please
share it. ROOTFS_POSTPROCESS_COMMAND seems to be buggy.
thank you
On Tue, Dec 12, 2017 at 1:58 PM, Mike Looijmans
mailto:mike.looijm...@topic.nl>
>>
wrote:
On 11-12-17 15:18, Sherif Omran wrote:
i want to create a recipe to clean some files from the rootfile
system, but i don't know how to let this recipe run the last
one
before building the rootfile system.
You can use ROOTFS_POSTPROCESS_COMMAND in your image recipe to do
some
last-minute filesystem cleanup.
However, in most cases it's much better to determine what recipe
puts the
files there and modify the recipe or remove the package. It would
help a
lot if you would reveal what files you want to remove and why.
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
>
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
___
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] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified
On 12/13/2017 03:16 AM, Robert Yang wrote: How about simply issuing 'git revert' after a build has failed? That's easier to implement than rearranging the order of commits, and the commit message can include a link to the build failure logs. Sounds reasonable to me, I will update the patch. Wait until I publish my devtool port, then if you could rebase on that, that'd be great! Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] recipe to clean up files from rootfs
here is my recipe, the aim was to remove some files from the init.d folder
and tweek before creating the image
#
# This file was derived from the 'Hello World!' example recipe in the
# Yocto Project Development Manual.
#
SUMMARY = "This recipe removes any missing files from the filesystem before
finalinzing it"
SECTION = "base"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
#SRC_URI = "file://*"
S = "${WORKDIR}"
BB_STRICT_CHECKSUM ="0"
ALLOW_EMPTY_${PN}="1"
#IMAGE_INSTALL = "packagegroup-core-boot packagegroup-base-extended
${CORE_IMAGE_EXTRA_INSTALL}"
#IMAGE_INSTALL = "${CORE_IMAGE}"
#inherit core-image
my_postprocess_function() {
rm -r ${D}${bindir}/init.d/psplash.sh
}
ROOTFS_POSTPROCESS_COMMAND += "my_postprocess_function; "
On Wed, Dec 13, 2017 at 7:22 AM, Mike Looijmans
wrote:
> Well, start by sharing yours first.
>
> Be careful when naming your shell routine, sometimes OE considers parts
> behind the underscore as overrides and then it cannot find it.
>
>
> On 13-12-17 07:14, Sherif Omran wrote:
>
>> hi Mike,
>> i could not get it to work, if you have a recipe that works, please share
>> it. ROOTFS_POSTPROCESS_COMMAND seems to be buggy.
>>
>> thank you
>>
>>
>>
>> On Tue, Dec 12, 2017 at 1:58 PM, Mike Looijmans > > wrote:
>>
>> On 11-12-17 15:18, Sherif Omran wrote:
>>
>> i want to create a recipe to clean some files from the rootfile
>> system, but i don't know how to let this recipe run the last one
>> before building the rootfile system.
>>
>>
>> You can use ROOTFS_POSTPROCESS_COMMAND in your image recipe to do some
>> last-minute filesystem cleanup.
>>
>> However, in most cases it's much better to determine what recipe puts
>> the
>> files there and modify the recipe or remove the package. It would
>> help a
>> lot if you would reveal what files you want to remove and why.
>>
>>
>> Kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>> TOPIC Products
>> Materiaalweg 4, NL-5681 RJ Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: +31 (0) 499 33 69 79 > 3%2069%2079>
>> E-mail: mike.looijm...@topicproducts.com
>>
>> Website: www.topicproducts.com
>>
>> Please consider the environment before printing this e-mail
>>
>>
>>
>> --
>>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Products
> Materiaalweg 4, NL-5681 RJ Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijm...@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
> ___
>
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
