I am updating the asterisk recipe to 13.16.0 to fix some security advisories
and hit an issue in the configuration script new to me:
config.log:
configure:17599: checking if we have usable eventfd support
configure:17602: error: in
`/home/chris/yocto/build/tmp/work/core2-32-poky-linux/asterisk/
When applying rpm updates generated by yocto, configuration files/directories
are overwritten with files from the rpm.
My spec file for generating equivalent native packages with rpmbuild specifies
these files with %config(noreplace) so that this overwriting does no occur.
Is it possible to get
Thanks Ross and Jussi,
python3native works in the short term and in the longer term I will look into
distutils/setuptools.
Cheers,
Chris
From: Burton, Ross
Sent: 05 May 2017 10:43
To: Chris Trobridge
Cc: Yocto List
Subject: Re: [yocto] Pre-compiling Python
To improve startup speed I have decided to pre-compile python3 byte code in my
bb recipe. This is done semi automatically with the rpm build for Fedora but
I've not found anything similar for Yocto.
I initially tried to use compileall:
python3 -m compileall ${D}/opt/test_app/python
This al
> From: yocto-boun...@yoctoproject.org on
> behalf of Alvaro Garcia >
> Sent: 07 April 2017 11:59
> To: yocto@yoctoproject.org
> Subject: [yocto] Customize live grub entries
> Hi, I want an unattended installation (just boot from USB, install, and
> remove USB). I am able to remove all ques
f poky for ones that are missing. I thought about the Linux
kernel site but nothing in bugzilla or archives and this may not be of
sufficient interest without more information.
Thanks,
Chris
From: yocto-boun...@yoctoproject.org on behalf
of Chris Trobridge
Sent: 24 February 2017 12:10
To: Yoc
Since switching kernel to 4.8 (Morty) I have noticed that sometimes my Intel
Atom hardware (Pokini) doesn't boot Linux.
Specifically, syslinux runs fine and starts the kernel but this then hangs
immediately after displaying "Booting the kernel.", producing no further output.
This is typical out
enabled since then. BUILD_NATIVE is
an option in their 'menuselect' so I need to configure that, as the clean
solution, rather than just patching their makeopts.
Regards,
Chris
From: Burton, Ross
Sent: 16 January 2017 15:40
To: Chris Trobridg
As noted previously , there have been various issues reported with
march=native, for a very long time, so I will try to see how to get that
removed from the build.
Chris
From: Leon Woestenberg
Sent: 16 January 2017 09:57
To: Chris Trobridge
Cc: Yocto Lis
se it may be more a case
of the compiler using core2 instructions that are not valid for atom.
Regards,
Chris
From: Leon Woestenberg
Sent: 16 January 2017 09:57
To: Chris Trobridge
Cc: Yocto List
Subject: Re: [yocto] Illegal Instruction Generate for Intel Atom
This arose building asterisk switching from 13.7 to 13.11+.
The executable core dumps immediately with an illegal instruction instruction,
which gdb reported as 'andn'. This is part of BMI1, which was introduced with
Haswell. I am targeting a (32-bit) Z5xx Atom processor, which predates this
On Mon, 2017-01-09 at 10:47 -0800, Khem Raj wrote:
> On Fri, Jan 6, 2017 at 3:52 AM, Chris Trobridge
> wrote:
> > I am getting "Exception: OSError: [Errno 7] Argument list too long"
> > for sign_rpm in the do_package_write_rpm tasks for the
> > linux-yocto and g
I am getting "Exception: OSError: [Errno 7] Argument list too long" for
sign_rpm in the do_package_write_rpm tasks for the
linux-yocto and glibc-locale recipes.
This is building core-image-minimal (and also my own image) with morty
(5aa481d) on Fedora 25.
I have enabled the rpm signing with:
Hi,
I have got around to updating these recipes and found a few issues:
asterisk has a autoconf macro file for pjproject in ./third-party/pjproject/,
which does not get picked up by autobuild.bbclass.
This uses find with a -maxdepth of 2 but but 3 would be needed. I found a temp
fix by cop
> Subject: Re: [yocto] QA python3 runtime dependency
> To: christrobri...@hotmail.com; yocto@yoctoproject.org
> From: s.mueller-klie...@phytec.de
> Date: Fri, 16 Sep 2016 14:38:37 +0200
>
> On 16.09.2016 13:45, Chris Trobridge wrot
I raised this back in April but I am back on QA review and I did not manage to
sort this at the time.
I have a recipe for pjproject that produces QA host contamination warnings for
all the library files it installs:
pjproject: /pjproject/usr/lib/*.so.2 is owned by uid 1000, which is the same as
My top-level python3 scripts have "#!/usr/bin/python3" and the recipe RDEDENDS
on python3.
There's no problem in the final system as python3 is present in /usr/bin as
expected.
What I do not understand is why I am getting a QA warning : "requires
/usr/bin/python3, but no providers found in RDEPE
Hi,
Since I switched to Krogoth systemd-networkd (229) is not setting up IPv4
networks but is deleting any manual configuration set up by 'ip addr'.
It is setting up a link-local IPv6 address and attempting auto-conf and DHCPv6
despite IPv6 not being enabled in the configuration.
I didn't manage
er 6.2 and 6.3)
Joël Esponde
Honeywell
| Sensing and Productivity Solutions
De : Chris Trobridge [mailto:christrobri...@hotmail.com]
Envoyé : mardi 10 mai 2016 13:28
À : Esponde, Joel; yocto@yoctoproject.org
Objet : RE: [yocto] Formulating Recipe for out-of-tree kernel module
T
to-boun...@yoctoproject.org]
De la part de Chris Trobridge
Envoyé : mardi 10 mai 2016 08:59
À : yocto@yoctoproject.org
Objet : Re: [yocto] Formulating Recipe for out-of-tree kernel module
At the risk of answering my own question...
Splitting a driver package into a module recipe an
At the risk of answering my own question...
Splitting a driver package into a module recipe and a separate recipe for
user-mode utilities works in that each recipe uses the appropriate build
process and puts files in the appropriate subdirectory of /work/.
I still don't see a way to build one out
I am looking to produce a recipe for the amfeltec usb-fxs adaptor
(http://amfeltec.com/products/piranha-usb-fxs-adapter/), with the intention of
contributing this to the meta-telephony layer.
However, I have found a few obstacles to getting a clean recipe:The makefile
produces both a kernel modu
> Subject: Re: [yocto] [Fwd: gobject introspection release notes]
> To: zhenhua@nxp.com; christrobri...@hotmail.com
> CC: yocto@yoctoproject.org
> From: alexander.kana...@linux.intel.com
> Date: Wed, 27 Apr 2016 15:38:01 +0300
>
> On 04/26/2016 11:05 AM, Zhenhua Luo wrote:
> > Any ideas as to
Regarding:
"Can you shine any light on the "-fdebug-prefix-map" related fatal QA errors?
(leaking host paths) I've found some discussion in openembedded that suggests
this should be fixed in the compiler but again I am curious why this (very
simple) recipe has this issue but others don't."
So D
ed.
'My' asterisk recipe is based on the one from meta-telephony so I should get in
touch with the authors.
Regards,Chris
From: ross.bur...@intel.com
Date: Wed, 27 Apr 2016 08:41:14 +0100
Subject: Re: [yocto] Build Errors with new recipe for pjproject
(autotools/pkgconfig)
To: christro
Aside from the issues I mentioned previously, pjproject is detecting
cross-compilation and this causes it to append '-x86_64-poky-linux-gnu' to all
its library names.
This is then breaking autotools configuration in other recipes that are testing
for the base name.
Is it common for a build proce
Hi Andreas,
In general, you should not add your changes to poky directly, or any of the
other provided layers.
In this case the 'permanent' way to do this is to produce your own distribution
layer but the quick alternative is to set the variable in conf/local.conf.
Regards,Chris
From: andreas.e
I have been trying to formulate a new recipe for pjproject (pjsip) - there was
one but it seems too old and isn't part of any layer now.
The library seems to require a fairly straightforward autotools/pkgconfig
recipe but I get two errors, both of which I can see have come up before but
haven't
Any ideas as to why "qemu-ppc64 crashes out immediately"?
I can confirm the build ends in a segfault when I tried building
gobject-introspection for the t1042d4rdb-64b machine.
I did get one qemu crash recorded by Fedora but the actual crash dumps
(appended) are for a PowerPC. That said, given
r
the BSP layers in Yocto website (http://git.yoctoproject.org/cgit.cgi/).
·
QorIQ ARM targets: meta-fsl-arm
·
QorIQ PPC targets: meta-fsl-ppc
Best Regards,
Zhenhua
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Chris Trobr
Has anyone attempted to use the Qoriq BSP layers with them main Yocto release
rather than the NXP (ex Freescale) SDK they come bundled in?
I ask because the NXP SDK is somewhat behind the main Yocto release schedule.
It should be easier to port the BSP to the current Yocto but I have no idea
what
> To: yocto@yoctoproject.org
> From: alexander.kana...@linux.intel.com
> Date: Thu, 7 Apr 2016 16:40:30 +0300
> Subject: Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2
>
> On 04/07/2016 04:35 PM, Burton, Ross wrote:
>
> > Yeah, that. :) Annoyingly it's not just a PACKAGECONFIG due to how
> From: ross.bur...@intel.com
> Date: Wed, 6 Apr 2016 12:22:39 +0100
> Subject: Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2
> To: christrobri...@hotmail.com
> CC: yocto@yoctoproject.org
>
>
> On 6 April 2016 at 12:19, Chris Trobri
com
Date: Wed, 6 Apr 2016 11:57:10 +0100
Subject: Re: [yocto] Python GObject Errors on yocto-2.1_M3.rc2
To: christrobri...@hotmail.com
CC: yocto@yoctoproject.org
On 6 April 2016 at 11:53, Chris Trobridge wrote:
ImportError: No module named importlib
Looks like python-gobject needs to depend on py
I have a code base using gobject introspection that has been running fine on
Alex's gobject-introspection-experimental branch on poky-contrib but is broken
on 2.1 M3.
I am using it with python3 (3.5) but it isn't accessible with python27 either.
It appears it may be partially installed for 2.
I hit this issue experimenting with disabling ipv6, as Todd did originally,
with an odd error about not being able to build the native sdk.
It's not a problem for me but is there a recommended way for disabling a libc
distro feature like ipv6 without creating a whole new distro? Does libc really
Hi,
I have been testing out the facility for generating signed RPMs.
It's currently failing to find
'build/tmp/sysroots/x86_64-linux/etc/RPM-GPG-PUBKEY', log listed at end.
I couldn't find a lot of documentation but from what I could find, I added the
following to local.conf:
INHERIT += " sign_rp
I was testing out a new image this afternoon and all was well until I fdisk'd
the partitions away on /dev/sda (with the live image booting from a usb stick
on /dev/sdc).
After this the image stopped booting and started complaining about all sorts of
FAT errors on /dev/sda and did not mount the r
(I posted this to openembedded-core but it appears to have got lost in the
noise!)
Hi,
I have been looking into producing a 'python3-dbus' recipe, based on the
python-dbus recipe.
This recipe outputs a couple of files that are version independent but end up
overlapping and causing the build t
39 matches
Mail list logo
