Well, I tried adding debug lines to poky/bitbake/lib/bb/cooker.py, and I think
what is happening is:
i) BSP has BBMASK = line.
ii) I add BBMASK_forcevariable = line to my local.conf
iii) If I check with -e option, I can see BBMASK variable is finally set to
""
iv) However, when
Hi,
I am currently trying to compile the linux-yocto-rt kernel for a custom
board (called iot2000 here) based on the Intel Galileo platform.
The build fails, because the kernel configuration isn't applied.
However, the bitbake environment of the linux-yocto-rt target looks
good to me and
On 16 September 2016 at 06:49, Martin Bachmann wrote:
> In my recipe I've added RDEPENDS += "opencv " and yocto installs the
> libraries in the target rootfs. But now i'd like the libraries compiled
> natively and installed to x86_x64-linux rootfs. This would allow me to
>
Hello,
how can I build ntp with openssl support?
I already created a ntp_%.bbappend file to extend the recipe ntp_4.2.8p4.bb.
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
PACKAGECONFIG += "openssl"
is this sufficant to enable openssl?
How can I determine if ntp supports sha1?
Best regards,
Hi everyone,
When attaching a Navilock GPS USB mouse to the device, the gpsd-script
(/lib/udev/gpsd.hotplug) is not triggered to start gpsd with
/dev/ttyACM0, that was found.
It seems, /etc/udev/rules.d/60-gpsd.rules does not get triggered. In
there, the line:
SUBSYSTEM!="tty",
Hi all,
I just finished a first beta version of a meta layer for SBC pine64.
You can find it in https://github.com/mont3z/meta-pine64
I'd appreciate if anyone has any comments on possible improvements. A
major problem I had was the necessity of two toolchains: one for
compiling u-boot (32 bits)
On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute wrote:
> Hello,
>
> how can I build ntp with openssl support?
>
> I already created a ntp_%.bbappend file to extend the recipe ntp_4.2.8p4.bb.
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
You don't really need this
On Fri, Sep 16, 2016 at 6:33 AM, Burton, Ross wrote:
>
> On 16 September 2016 at 13:40, Chris Trobridge
> wrote:
>>
>> The install line in the makefile is "cp -af $(APP_LIBXX_FILES)
>> $(DESTDIR)$(libdir)/", so I am at a bit of a loss as this
On Fri, Sep 16, 2016 at 5:15 AM, Takashi Matsuzawa
wrote:
> OK, I figured this out that I can add my BBMASK lines to my
> conf/distro/xxx.conf fille.
>
> So that I can append to what BSP defines and it seems to happen before
> collect_bbbfiles() function.
An
OK, I figured this out that I can add my BBMASK lines to my
conf/distro/xxx.conf fille.
So that I can append to what BSP defines and it seems to happen before
collect_bbbfiles() function.
Sorry for my confusion.
From: Takashi Matsuzawa
Sent: Friday, September
Also, buildset-config.controller/nightly.conf needs to be edited and
the rule for luna removed.
-Bill
On Fri, Sep 16, 2016 at 5:07 AM, Joshua Lock
wrote:
> On Thu, 2016-09-15 at 22:08 -0700, Graydon, Tracy wrote:
>> We are no longer supporting kepler or luna.
Great catch, thanks Bill.
I've pushed a patch to make this change.
Thanks,
Joshua
On Fri, 2016-09-16 at 07:24 -0700, Bill Randle wrote:
> Also, buildset-config.controller/nightly.conf needs to be edited and
> the rule for luna removed.
>
> -Bill
>
> On Fri, Sep 16, 2016 at 5:07 AM,
On 16 September 2016 at 13:40, Chris Trobridge
wrote:
> The install line in the makefile is "cp -af $(APP_LIBXX_FILES)
> $(DESTDIR)$(libdir)/", so I am at a bit of a loss as this should preserve
> ownership.
>
It does - the build happens as you (uid 1000) so the file
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
> 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 wrote:
>> My top-level
On 16.09.2016 13:45, Chris Trobridge wrote:
> My top-level python3 scripts have "#!/usr/bin/python3" and the recipe
> RDEDENDS on python3.
I guess this is what you need:
RDEPENDS_${PN} = "python3-core"
As the interpreter is in the -core package.
Regards, Stefan
> There's no problem in the
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
Claudius, I am running into similar issues with linux-yocto-rt. I am working
out of poky/krogoth.
I have the following two lines set at the end of local.conf
COMPATIBLE_MACHINE_genericx86 = "genericx86"
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
I also have MACHINE ?= "genericx86"
Hi!
It maybe is a naive question and I assume it's not possible because I didn't
find anything related in the manual.
Is it possible to launch a toaster instance on an already command-line-setup
build?
Like inheriting the toaster bbclass and maybe some magic trick?
Or am I stuck in
Current Dev Position: YP 2.2 M4 (M3 is in QA)
Next Deadline: YP 2.2 M4 which will be Oct. 3rd (5:00pm GMT)
SWAT team rotation: Jussi -> Maxin
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
*The M3rc1 build built mostly cleanly and is in QA. We
Not using the yocto LDFLAGS will make some qa tests fail:
ERROR: wiringpi-git-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary:
'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/packages-split/wiringpi/usr/lib/libwiringPi.so.2.32'
No GNU_HASH in the elf
Not having this correctly will get you into troubles like:
| gpio.c:40:23: fatal error: gertboard.h: No such file or directory
| #include
Signed-off-by: Andrei Gherzan
---
recipes-devtools/wiringPi/wiringpi_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Signed-off-by: Andrei Gherzan
---
recipes-devtools/wiringPi/wiringpi_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-devtools/wiringPi/wiringpi_git.bb
b/recipes-devtools/wiringPi/wiringpi_git.bb
index 9d2206b..f2cacd3 100644
---
ERROR: bcm2835-1.50-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary:
'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/spi'
No GNU_HASH in the elf binary:
Thank you all for jumping on this. Very much appreciated.
--Tim
On Fri, Sep 16, 2016 at 7:37 AM, Joshua Lock
wrote:
> Great catch, thanks Bill.
>
> I've pushed a patch to make this change.
>
> Thanks,
>
> Joshua
>
> On Fri, 2016-09-16 at 07:24 -0700, Bill Randle
On Tue, Sep 13, 2016 at 12:06:11PM +1000, Jonathan Liu wrote:
> The IMAGE_NAME variable already contains the date and time so it is
> redundant to also include the date again with IMAGEDATESTAMP
> when writing to image-version-info in the boot partition.
>
> Signed-off-by: Jonathan Liu
26 matches
Mail list logo