Re: [yocto] Adding openjdk-11 to Yocto

2023-03-27 Thread Robert Joslyn
e, David via lists.yoctoproject.org > Sent: Thursday, February 2, 2023 8:02 AM > To: Richard Leitner ; Robert Joslyn > > Cc: yocto@lists.yoctoproject.org > Subject: [EXTERNAL] Re: [yocto] Adding openjdk-11 to Yocto > > CAUTION: This email originated from outside of Parraid.

Re: [yocto] Adding openjdk-11 to Yocto

2023-02-01 Thread Robert Joslyn
> On Feb 1, 2023, at 2:26 AM, Richard Leitner wrote: > > Hi, > > On Tue, Jan 31, 2023 at 06:39:08AM -0800, Robert Joslyn wrote: >> >>> On Jan 30, 2023, at 12:27 PM, Richard Leitner >>> wrote: >>> >>> Hi David, >>> unfortun

Re: [yocto] Adding openjdk-11 to Yocto

2023-01-31 Thread Robert Joslyn
> On Jan 30, 2023, at 12:27 PM, Richard Leitner > wrote: > > Hi David, > unfortunately none I'm aware of. > > But if you have time to add java 11 (or newer) support to meta-java I can > give support/guidance. > > regards;rl Is there any interest in adding recipes that install pre-built

Re: [yocto] Howto build packages for dependencies of an out of image recipe build.

2022-03-09 Thread Robert Joslyn
> On Mar 9, 2022, at 4:59 AM, Daniel Squires wrote: > > Just to be absolutely clear, here is the result of having run bitbake > build-essential having first removed and thus started with a clean tmp dir. > > dan@melon:/home/dan/workspace_ssd/kas/build$ find tmp/deploy/deb/ > tmp/deploy/deb/

Re: [yocto] Building Yocto on M1 Mac

2022-02-14 Thread Robert Joslyn
> On Feb 14, 2022, at 4:02 AM, Ross Burton wrote: > > On Mon, 14 Feb 2022 at 00:17, Robert Joslyn > wrote: >> On my 2020 M1 MacBook Air (8 cores, 16 GB RAM, docker using 8 cores and 8 >> GB), the build took 84 minutes. My desktop with an AMD Ryzen 9 3950X (16 >>

Re: [yocto] Building Yocto on M1 Mac

2022-02-13 Thread Robert Joslyn
> On Feb 13, 2022, at 6:56 AM, Abhijeet Tripathi > wrote: > > > On Sun, Feb 13, 2022 at 7:09 PM Anders Montonen > wrote: > Hi, > >> On 13 Feb 2022, at 14:24, Abhijeet Tripathi >> wrote: >> >> Hello yocto-devs, >> >> I'm new to the yocto project and trying to set up a build environment

Re: [yocto] Packages Missing from Deploy

2022-01-23 Thread Robert Joslyn
> On Jan 19, 2022, at 9:17 PM, Robert Joslyn > wrote: > > I’m testing migrating one of my dunfell builds to master in anticipation of > the upcoming LTS, and there is a difference in how packages are populated > into deploy that is causing me problems. My builds

[yocto] Packages Missing from Deploy

2022-01-19 Thread Robert Joslyn
I’m testing migrating one of my dunfell builds to master in anticipation of the upcoming LTS, and there is a difference in how packages are populated into deploy that is causing me problems. My builds use a package feed, and the way I’ve been generating my package feed is to create a

[yocto] [meta-gplv2][PATCH] conf/distro: Restore btrfs-tools since it was relicensed

2021-05-11 Thread Robert Joslyn
libbtrfsutil was relicensed from LGPL-3.0+ to LGPL-2.1+, so it is no longer necessary to remove btrfs-tools. Signed-off-by: Robert Joslyn --- conf/distro/include/disable-gplv3.inc | 1 - 1 file changed, 1 deletion(-) diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include

Re: [yocto] Recipe Grep'ing

2021-05-08 Thread Robert Joslyn
On Wed, 2021-05-05 at 17:50 -0700, Khem Raj wrote: > > > On 5/5/21 5:41 PM, Chuck Wolber wrote: > > I was pondering putting some work in to a fairly large patch set > > aimed > > at making recipes easier to grep through, and wanted to get some > > feedback before I put time and effort into it.

Re: [yocto] [meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

2021-04-19 Thread Robert Joslyn
Just to clarify, btrfs-tools has always had an LGPL-3.0 library (libbtrfsutil), the recipe just never declared it before. Upstream is relicensing that library to LGPL-2.1+, which should be done for the next release. Sorry about this, I sent the update and didn’t realize it broke the non-gplv3

Re: [yocto] [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors

2020-08-03 Thread Robert Joslyn
pmbuild: not found > WARNING: exit code 127 from a shell command. > > Did you also encounter this ? My builds normally use ipk, but I tried rpm on one and did not see this error when building icedtea7-native. Sorry! Thanks, Robert > Cheers > Jeff > > On 7/28/20 5:28

Re: [yocto] [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors

2020-07-27 Thread Robert Joslyn
On Mon, 2020-07-27 at 06:16 -0700, ithi...@gmail.com wrote: > Hi, > > I am trying to build openjdk-8-native, however its icedtea7 dependency > fails to build. > The error is a little hard to parse but it appears to be due to warnings > being treated as errors. > There are a lot of logs like the

[yocto] Errors Building openjdk-8 on dunfell

2020-06-29 Thread Robert Joslyn
I'm trying to build openjdk-8 on dunfull and am getting some build errors. Using an Ubuntu 18.04 host, I get an error building the openjdk-8 recipe: | g++: error: unrecognized command line option ‘-fmacro-prefix- map=/mnt/yocto/bionic/poky/build/tmp/work/core2-64-poky-linux/openjdk-

[yocto] update_gio_module_cache Fails with systemd-firstboot

2019-12-18 Thread Robert Joslyn
I have a simple image using the poky distro and I'd like to add systemd- firstboot support. I have a bbappend to systemd enabling the PACKAGECONFIG option, but then I get an error in do_rootfs: ERROR: The postinstall intercept hook 'update_gio_module_cache' failed, details in