[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT)
All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PDT tomorrow. Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto Wiki: https://www.yoctoproject.org/public-virtual-meetings/ WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time Where Zoom Meeting: https://zoom.us/j/990892712 (map) Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 •Cell: (208) 244-4460 • Email:stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] native perl build wants to run target shared object
Hi,
I'm trying to add a recipe for a new perl package: linux-inotify.
It's fairly standard package available in cpan[1].
I added the following DEPENDS and RDEPENDS:
RDEPENDS_${PN} += " \
perl \
perl-module-base \
"
DEPENDS += " \
perl-native \
libmodule-build-perl-native \
"
But I'm getting the following build error:
ERROR: linux-inotify-perl-0.05-r0 do_compile: oe_runmake failed
ERROR: linux-inotify-perl-0.05-r0 do_compile: Function failed:
do_compile (log file is located at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/temp/log.do_compile.15693)
ERROR: Logfile of failure stored in:
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/temp/log.do_compile.15693
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 40 PASTHRU_INC= -O2 -pipe -g
-feliminate-unused-debug-types
-fdebug-prefix-map=//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0=/usr/src/debug/linux-inotify-perl/0.05-r0
-fdebug-prefix-map=//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot=
-fdebug-prefix-map=//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native=
LD=aarch64-poky-linux-gcc
--sysroot=//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot
|
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native/usr/bin/perl-native/perl
Build --makefile_env_macros 1
| Can't load
'//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot/usr/lib/perl/5.24.1/auto/File/Glob/Glob.so'
for module File::Glob:
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot/usr/lib/perl/5.24.1/auto/File/Glob/Glob.so:
cannot open shared object file: No such file or directory at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native/usr/bin/perl-native/../../../usr/lib/perl-native/perl/5.24.1/XSLoader.pm
line 96.
| at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot/usr/lib/perl/5.24.1/File/Glob.pm
line 68.
| Compilation failed in require at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native/usr/bin/perl-native/../../../usr/lib/perl-native/perl/vendor_perl/5.24.1/Module/Build/Base.pm
line 1263.
| BEGIN failed--compilation aborted at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native/usr/bin/perl-native/../../../usr/lib/perl-native/perl/vendor_perl/5.24.1/Module/Build/Base.pm
line 1263.
| Compilation failed in require at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native/usr/bin/perl-native/../../../usr/lib/perl-native/perl/vendor_perl/5.24.1/Module/Build.pm
line 17.
| BEGIN failed--compilation aborted at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/recipe-sysroot-native/usr/bin/perl-native/../../../usr/lib/perl-native/perl/vendor_perl/5.24.1/Module/Build.pm
line 17.
| Compilation failed in require at Build line 47.
| BEGIN failed--compilation aborted at Build line 47.
| Makefile:33: recipe for target 'all' failed
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING:
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/temp/run.do_compile.15693:1
exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at
//build/tmp/work/aarch64-poky-linux/linux-inotify-perl/0.05-r0/temp/log.do_compile.15693)
ERROR: Task
(//meta-/recipes-perl/linux-inotify/linux-inotify-perl_0.05.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 3669 tasks of which 3667 didn't need to
be rerun and 1 failed.
Apparently the XSLoader module tries to use glob but instead of
loading the host shared object it opens the target shared object and
fails.
I couldn't find any reason nor fix for that. Would appreciate any help.
Best regards,
Bartosz Golaszewski
[1] https://metacpan.org/pod/Linux::Inotify
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Unassigned Bugs - Help Needed
All, The triage team meets weekly and does its best to handle the bugs reported into the bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 313 unassigned bugs. We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6". Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (stephen.k.jol...@intel.com) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] (How) did you script bitbake/set up nightly builds?
It seems the call doesn't work correctly with dash (ls -la /bin/sh):
subprocess.call(". oe/oe-init-build-env; ls", shell = True)
/bin/sh: 51: .: Can't open root_dir/scripts/oe-buildenv-internal
Specifying bash explicitly works ok:
subprocess.call(". oe/oe-init-build-env; ls", shell = True,
executable="/bin/bash")
### Shell environment set up for builds. ###
...
...
On Fri, Aug 31, 2018 at 1:47 PM, Burton, Ross wrote:
> On 31 August 2018 at 12:45, Alan Martinovic
> wrote:
> > Fair enough, I gave an example with a simple workaround. :)
> >
> > But you do have a point there, if I'm getting you answer right on a
> broader
> > level.
> > Is it something like this?
> >
> >> Instead of setting the environment only once and running bitbake
> multiple
> >> times
> >> just make the environment sourcing and bitbake execution an atomic
> >> operation.
> >
> >
> > So if I wanted to automate i.e.:
> >
> > . oe-init-build-env mybuild
> > bitbake -c cleanall failure_prone_package
> > bitbake failure_prone_package
> > bitbake foo #image build
> >
> > It's fine to do it like this:
> >
> > subprocess.call(". oe-init-build-env mybuild ; bitbake -c cleanall
> > failure_prone_package", shell=True)
> > subprocess.call(". oe-init-build-env mybuild ; bitbake
> > failure_prone_package", shell=True)
> > subprocess.call(". oe-init-build-env mybuild ; bitbake foo", shell=True)
>
> Yes, that's exactly the idiom. The alternative would be to invoke
> oe-init-build-env once and then run export, and parse that to
> construct an environment to pass to future bitbake calls. That would
> work, but would be more complex.
>
> Ross
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] chromium is compiling but is not able to add in the image
"Pandey, Kamal" writes: > I tried adding chromium package via the meta-browser layer. It is > compiling when I run $ bitbake chromium . But when I run $bitbake > core-image-minimal-pdm3. It’s not adding chromium to the image and > throwing errors as shown below: "chromium" is currently just a shorthand for "chromium-x11". Does it work if you pass the latter to bitbake? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] mono build issue
Hi Matthew, > The problem still exists sadly. > Matthew I had the same issue. The problem was that I installed Mono on my host system. After removing it and reforcing a rebuild of the mono package and its dependencies the error has gone: # sudo apt-get purge libmono* cli-common mono-runtime # bitbake mono -C compile --force I did to spend any more time on fixing the recipe. Best regards -Carsten -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
