date:20230220

Re: [yocto] trying to install files when those files already exist

2023-02-20 Thread Khem Raj

On Mon, Feb 20, 2023 at 8:20 PM Mistyron  wrote:
>
> Hi,
>
> I'm running into a "is trying to install files into a shared area when those 
> files already exist." error and am not sure how to resolve it. I get the 
> following:
>
> ERROR: linux-renesas-5.10.83-cip1+gitAUTOINC+e52825e45b-r1 do_packagedata: 
> The recipe linux-renesas is trying to install files into a shared area when 
> those files already exist. Those files and their manifest location are:
>   
> /home/yocto/rzg_vlp_v3.0.0/build/tmp/pkgdata/smarc-rzg2l/runtime/kernel-module-cfg80211-5.10.83-cip1-yocto-standard
> (matched in 
> manifest-smarc_rzg2l-kernel-module-lwb5p-backports-laird.packagedata)
>   
> /home/yocto/rzg_vlp_v3.0.0/build/tmp/pkgdata/smarc-rzg2l/runtime/kernel-module-cfg80211-5.10.83-cip1-yocto-standard.packaged
> (matched in 
> manifest-smarc_rzg2l-kernel-module-lwb5p-backports-laird.packagedata)
>   
> /home/yocto/rzg_vlp_v3.0.0/build/tmp/pkgdata/smarc-rzg2l/runtime/lib32-kernel-module-cfg80211-5.10.83-cip1-yocto-standard
> (matched in 
> manifest-smarc_rzg2l-kernel-module-lwb5p-backports-laird.packagedata)
> Please verify which recipe should provide the above files.
>
> It obviously has something to do with the drivers for the lwb5p laird module 
> I'm trying to add.
>
> How do I go about resolving this on my dunfell based build?
>

there are two recipes building same files which end up in same
location on target rootfs. So you should either disable the in-kernel
module or not include out of kernel module recipe
> --
> RON EGGLER Firmware Engineer (he/him/his) www.mistywest.com
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59264): https://lists.yoctoproject.org/g/yocto/message/59264
Mute This Topic: https://lists.yoctoproject.org/mt/97102802/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] trying to install files when those files already exist

2023-02-20 Thread Mistyron


Hi,

I'm running into a "is trying to install files into a shared area when 
those files already exist." error and am not sure how to resolve it. I 
get the following:


ERROR: linux-renesas-5.10.83-cip1+gitAUTOINC+e52825e45b-r1 
do_packagedata: The recipe linux-renesas is trying to install files into 
a shared area when those files already exist. Those files and their 
manifest location are:

/home/yocto/rzg_vlp_v3.0.0/build/tmp/pkgdata/smarc-rzg2l/runtime/kernel-module-cfg80211-5.10.83-cip1-yocto-standard
    (matched in 
manifest-smarc_rzg2l-kernel-module-lwb5p-backports-laird.packagedata)

/home/yocto/rzg_vlp_v3.0.0/build/tmp/pkgdata/smarc-rzg2l/runtime/kernel-module-cfg80211-5.10.83-cip1-yocto-standard.packaged
    (matched in 
manifest-smarc_rzg2l-kernel-module-lwb5p-backports-laird.packagedata)

/home/yocto/rzg_vlp_v3.0.0/build/tmp/pkgdata/smarc-rzg2l/runtime/lib32-kernel-module-cfg80211-5.10.83-cip1-yocto-standard
    (matched in 
manifest-smarc_rzg2l-kernel-module-lwb5p-backports-laird.packagedata)

Please verify which recipe should provide the above files.

It obviously has something to do with the drivers for the lwb5p laird 
module I'm trying to add.


How do I go about resolving this on my dunfell based build?

--
RON EGGLER Firmware Engineer (he/him/his) www.mistywest.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59263): https://lists.yoctoproject.org/g/yocto/message/59263
Mute This Topic: https://lists.yoctoproject.org/mt/97102802/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] fltk recipe fails

2023-02-20 Thread Mistyron


Hi Takayasu,

Thank you for this. I have cloned the fltk/ dir from the dunfell branch 
to my build host. This seemed to help out with the fltk issue but I have 
to suspend work on this for now.


Thanks,

Ron

On 2/20/23 00:23, Takayasu Ito wrote:

Hi Ron

The patch file can be found at
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/fltk/fltk 




On 2023/02/20 16:51, Mistyron wrote:

Hi,

I need too build fltk but the recipe from openembedded 
(http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/fltk/fltk.bb?h=master) 
requires a patch file that I could not find. Hence I built my own 
recipe which looks something like:

[fltk.bb]
SUMMARY = "Fast Light Toolkit (FLTK) is a cross-platform GUI 
development library."
DESCRIPTION = "FLTK provides modern GUI functionality without the 
bloat and supports 3D graphics via OpenGL and its built-in GLUT 
emulation."


LICENSE = "LGPLv2.1+"
LIC_FILES_CHKSUM = "file://COPYING;md5=353c9fd4163eef6500f7e057aed0b083"

SRCREV = "master"
SRC_URI = "git://github.com/fltk/fltk.git;branch=${SRCREV}"

S = "${WORKDIR}/git"

inherit autotools

do_configure_prepend() {
 ${WORKDIR}/git/autogen.sh
}
[/fltk.bb]

I'm running into an issue with autoge.sh tho, the script appears simple:
[autogen.sh]
#! /bin/sh
#
# This file is no longer referred to in the documentation, it's kept
# for backwards compatibility only.
#
# Just run `autoconf` instead to generate `configure` and you're done.
#
# The old README.Unix.txt stated that it should be executed from within
# the "FLTK source-code directory", hence changing directories is not
# useful and would break if the user's home directory contained spaces.
# Changing directories has been removed in FLTK 1.4.0 and this file
# has been simplified substantially.
#
# Instead of executing it as documented in pre-1.4 README files the 
new docs
# instruct to just execute `autoconf` which is sufficient and 
equivalent to

# the old instructions.

autoconf --force || exit 1

test -n "$NOCONFIGURE" || ./configure "$@"
[/autogen.sh]

However, when I attempt to build my image, I get something like:
DEBUG: Executing shell function do_configure
autoconf: error: no input file
WARNING: exit code 1 from a shell command.
ERROR: Execution of 
'/home/yocto/rzg_vlp_v3.0.0/build/tmp/work/aarch64-poky-linux/fltk/1.0-r0/temp/run.do_configure.242968' 
failed with exit code 1


The autoconf man page states:

"-f, --force
consider all files obsolete"
i.e. I would expect it to work w/o any input files. What am I missing 
and how can I get fltk built succesfully?













--
RON EGGLER Firmware Engineer (he/him/his) www.mistywest.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59262): https://lists.yoctoproject.org/g/yocto/message/59262
Mute This Topic: https://lists.yoctoproject.org/mt/97082226/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Asking for advice on how to establish license compliance

2023-02-20 Thread Manuel Wagesreither

Hi all,

I'd like to ensure license compliance for an embedded product I'm working on.

Disclaimer: I've read 
https://docs.yoctoproject.org/dev/dev-manual/licenses.html and know about 
yoctos abilites to provide the license text and/or the source code. Still I 
feel I'm missing the key info of finding out the recipes I've actually got to 
do one thing and/or the other for? (Providing license text and/or source code.)

And in case of licenses requiring the release of the source code if modified: 
How do I check wether yocto uses the original software or applies patches and 
is therreby modifying the source code?

I'd like to know how you people deal with this in practice. Or do you employ 
the sledge hammer method of just releasing the source code of every single 
package you're using + putting all the licenses on the actual device? But in 
some cases, that might not be the right thing to do either.

Are there some licenses I should try to never ever get on my device? A.k.a. 
blocklist. Heard GPLv3 is such a candidate.

I'd be interested in a very simple guide on what to do for every single license:
* License W: Keep source secret and put license text on image
* License X: You don't need to worry about anything
* License Y: Release source code and put license text on image
* Lizense Z: Release source code if modified and put license text on image

Last but not least I'm very open for recommendations of a legal counsil in 
Vienna, Austria who can help me with software license compliance.

Thank you all,
Manuel

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59261): https://lists.yoctoproject.org/g/yocto/message/59261
Mute This Topic: https://lists.yoctoproject.org/mt/97094123/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW07

2023-02-20 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW07 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  10061

Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing 
nicely

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.2 M2

4.2 M3


 

  10731

bitbake --observe-only doesn't work with memres

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M2

4.2 M3


 

  11704

Add other resource monitoring options to conf/local.conf STOPTASKS/ABORT

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M4


 

  11781

bitbake --observe-only may get KeyError

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

4.2 M2

4.2 M3


 

  11899

broken 'bitbake --status-only' and 'bitbake -m' for multiple connections

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

4.2 M2

4.2 M3


 

  12279

enhance manifest not found warning

randy.macl...@windriver.com

newco...@yoctoproject.org

4.2 M2

4.2 M3


 

  13533

Devtool finish on _git package with SRCPV in PV points to wrong WORKDIR

randy.macl...@windriver.com

saul.w...@windriver.com

4.2 M2

4.2 M3


 

  13808

do_task[noexec] = "" marks task noexec, which is inconsistent with docs

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

4.2 M2

4.2 M3


 

  13980

Investigate replacements for PhantomJS for buildperf output

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M4


 

  14066

bitbake core-image-base -c populate_sdk fails when image contains bash, 
core-utils and package_deb is used

randy.macl...@windriver.com

pa...@zhukoff.net

4.2 M2

4.2 M3


 

  14125

busybox wget ssl is exposed to MitM attack due to CVE-2018-1000500

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14141

devtool modify fails with submodules

randy.macl...@windriver.com

s...@bigsur.com

4.2 M2

4.2 M3


 

  14165

AB-INT PTEST: strace ptest intermittent failure in qual_fault-syscall.test

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14311

valgrind drd/tests ptest intermittent failure

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14430

valgrind memcheck/tests/linux/stack_changes failure

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14443

valgrind none/tests/amd64/fb_test_amd64 ptest intermittent failure

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M4


 

  14466

python: Should we add this optimization: -fno-semantic-interposition for 1.3x 
speed improvment?

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14564

AB-INT: udev worker vda timeout

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14572

mozjs doesn't build for armv5

randy.macl...@windriver.com

jon.ma...@arm.com

4.2 M2

4.2 M3


 

  14677

systemd.SystemdServiceTests.test_systemd_disable_enable intermittent failure: 
no filesystem space on target

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14693

cmake-native do_configure fails when rebuilding without sstate on NIS hosts

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14689

Need to show activity when talking to hash equivalence servers

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.2 M2

4.2 M3


 

  14710

Improve cargo fetcher test cases

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M4


 

  1

[yocto] Enhancements/Bugs closed WW07!

2023-02-20 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

6


richard.pur...@linuxfoundation.org

3


thr...@amazon.de

1


ross.bur...@arm.com

1


Grand Total

11

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59259): https://lists.yoctoproject.org/g/yocto/message/59259
Mute This Topic: https://lists.yoctoproject.org/mt/97093379/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.2

2023-02-20 Thread Stephen Jolley

All,

Below is the list as of top 32 bug owners as of the end of WW07 of who have
open medium or higher bugs and enhancements against YP 4.2.   There are 47
possible work days left until the final release candidates for YP 4.2 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

33


randy.macl...@windriver.com

27


richard.pur...@linuxfoundation.org

25


ross.bur...@arm.com

24


david.re...@windriver.com

23


bruce.ashfi...@gmail.com

20


jpewhac...@gmail.com

10


pa...@zhukoff.net

8


saul.w...@windriver.com

6


sakib.sa...@windriver.com

6


pi...@toganlabs.com

4


tim.orl...@konsulko.com

4


sundeep.kokko...@gmail.com

3


s...@bigsur.com

2


naveen.go...@windriver.com

2


rybczyn...@gmail.com

2


alexandre.bell...@bootlin.com

2


jon.ma...@arm.com

2


alexis.loth...@bootlin.com

2


yashinde...@gmail.com

1


sundeep.kokko...@windriver.com

1


yoann.con...@smile.fr

1


mhalst...@linuxfoundation.org

1


hongxu@windriver.com

1


chee.yang@intel.com

1


mathew.pro...@gmail.com

1


zheng@windriver.com

1


jens.ge...@desy.de

1


louis.ran...@syslinbit.com

1


tvgamb...@gmail.com

1


martin.ja...@gmail.com

1


thomas.per...@bootlin.com

1


Grand Total

218

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59258): https://lists.yoctoproject.org/g/yocto/message/59258
Mute This Topic: https://lists.yoctoproject.org/mt/97093291/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-02-20 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, 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 408
unassigned or newcomer 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 four different "priority" classes
right now,  "4.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.3".

 

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 (sjolley.yp...@gmail.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_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59257): https://lists.yoctoproject.org/g/yocto/message/59257
Mute This Topic: https://lists.yoctoproject.org/mt/97093254/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Can I specify a prebuilt version of toolchain only for kernel building?

2023-02-20 Thread Khem Raj

On Mon, Feb 20, 2023 at 7:40 AM Y. HB  wrote:
>
> Hello
>
> I got a board (Rockchip RV1126), whose NPU driver  kernel module is
> distributed in binary form, which requires specific kernel version
> (4.19.111) and toolchain version (gcc 10.3)
>
> ( I built the yocto with the specified kernel version, but using yocto
> shipped gcc 11, when I insmod, the driver reported invalid module
> format, and modprobe reported invalid exec format, I guess that is due
> to gcc version is incompatible )
>
> I'm building the system with yocto kirkstone, which ships gcc 11. Can
> I have some way to just specify using external toolchain with prebuilt
> gcc 10.3 while other system still be built with default yocto shipped
> toolchain?

before we start on that path, perhaps verify that you can run the kernel
that you build with gcc 10.3 externally but manually building it and replacing
it on target
you can use a prebuilt toolchain from
https://toolchains.bootlin.com/releases_aarch64.html

>
> I have seen meta-external-toolchain and meta-soucery, but it seems it
> will replace whole toolchain with this external version. Can I find a
> mean to just specify for building  kernel ?
>
> Thanks
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59256): https://lists.yoctoproject.org/g/yocto/message/59256
Mute This Topic: https://lists.yoctoproject.org/mt/97088202/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Can I specify a prebuilt version of toolchain only for kernel building?

2023-02-20 Thread Y. HB

Hello

I got a board (Rockchip RV1126), whose NPU driver  kernel module is
distributed in binary form, which requires specific kernel version
(4.19.111) and toolchain version (gcc 10.3)

( I built the yocto with the specified kernel version, but using yocto
shipped gcc 11, when I insmod, the driver reported invalid module
format, and modprobe reported invalid exec format, I guess that is due
to gcc version is incompatible )

I'm building the system with yocto kirkstone, which ships gcc 11. Can
I have some way to just specify using external toolchain with prebuilt
gcc 10.3 while other system still be built with default yocto shipped
toolchain?

I have seen meta-external-toolchain and meta-soucery, but it seems it
will replace whole toolchain with this external version. Can I find a
mean to just specify for building  kernel ?

Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59255): https://lists.yoctoproject.org/g/yocto/message/59255
Mute This Topic: https://lists.yoctoproject.org/mt/97088202/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] AlmaLinux 8.5 support in Langdale

2023-02-20 Thread Chaplin, Kris via lists.yoctoproject.org


Thanks Alex,


Note that the list of supported host distros is set only for the poky
reference distro with a weak assignment, and not for oe-core or yocto
as a whole. If you do your own tests, and they don't show issues, you
can mark any distro as compatible, or install buildtools tarball to
insulate your build from problematic host tools (such as native gcc
compiler).
That's understood - thank you.  As there were some changes upstream, I 
wanted to ensure that we have as much overlap as possible, so customers 
looking to integrate our meta layers together with others would have a 
tried and tested path.

AlmaLinux in particular is a spinoff of RHEL and thus extremely
conservative within the same major version.


Yes - my assumption is that we should be ok with 8.x, but we always test 
against a specific version / versions and document these, to save any 
corner cases causing unexpected failures.


Appreciate the help.

Regards
Kris


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59254): https://lists.yoctoproject.org/g/yocto/message/59254
Mute This Topic: https://lists.yoctoproject.org/mt/97084127/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] AlmaLinux 8.5 support in Langdale

2023-02-20 Thread Chaplin, Kris via lists.yoctoproject.org


On 20/02/2023 12:11, Richard Purdie wrote:

We're testing against AlmaLinux 8.7 so I think this is a documentation
issue and the value hasn't been updated to match what we're now testing
against. I've updated master and I suspect we'll follow up with changes
to the other release branches.

Thanks for mentioning it.

Cheers,

Richard


Thank you Richard - that's great info.  I'll ask our team to do the same.

Regards
Kris


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59253): https://lists.yoctoproject.org/g/yocto/message/59253
Mute This Topic: https://lists.yoctoproject.org/mt/97084127/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] AlmaLinux 8.5 support in Langdale

2023-02-20 Thread Alexander Kanavin

Note that the list of supported host distros is set only for the poky
reference distro with a weak assignment, and not for oe-core or yocto
as a whole. If you do your own tests, and they don't show issues, you
can mark any distro as compatible, or install buildtools tarball to
insulate your build from problematic host tools (such as native gcc
compiler).

AlmaLinux in particular is a spinoff of RHEL and thus extremely
conservative within the same major version.

Alex

On Mon, 20 Feb 2023 at 12:58, Chaplin, Kris via lists.yoctoproject.org
 wrote:
>
> Hello,
>
> I'm working with our team to test supported development OS for our
> AMD/Xilinx PetaLinux distribution built on top of Langdale. The official
> supported Linux distributions are Ubuntu, Fedora, AlmaLinux, Debian and
> OpenSUSE, so we regtest our flow on each of these prior to advertising
> support.
>
> However, the supported version of AlmaLinux for Langdale is 8.5, and
> this is not available for download any more
> (https://mirrors.almalinux.org/isos.html).  The earliest version is 8.6,
> with 8.7 being most current.  The 8.5 isos are stripped from the
> mirrors, so url-games dont work here either.
>
> What is the recommended verison of AlmaLinux to test against Langdale?
> Is there a plan to update the Yocto release notes to reflect this?
>
> Many thanks
> Kris
>
>
>
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59252): https://lists.yoctoproject.org/g/yocto/message/59252
Mute This Topic: https://lists.yoctoproject.org/mt/97084127/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] AlmaLinux 8.5 support in Langdale

2023-02-20 Thread Richard Purdie

On Mon, 2023-02-20 at 09:12 +, Chaplin, Kris via
lists.yoctoproject.org wrote:
> Hello,
> 
> I'm working with our team to test supported development OS for our 
> AMD/Xilinx PetaLinux distribution built on top of Langdale. The official 
> supported Linux distributions are Ubuntu, Fedora, AlmaLinux, Debian and 
> OpenSUSE, so we regtest our flow on each of these prior to advertising 
> support.
> 
> However, the supported version of AlmaLinux for Langdale is 8.5, and 
> this is not available for download any more 
> (https://mirrors.almalinux.org/isos.html).  The earliest version is 8.6, 
> with 8.7 being most current.  The 8.5 isos are stripped from the 
> mirrors, so url-games dont work here either.
> 
> What is the recommended verison of AlmaLinux to test against Langdale?  
> Is there a plan to update the Yocto release notes to reflect this?

We're testing against AlmaLinux 8.7 so I think this is a documentation
issue and the value hasn't been updated to match what we're now testing
against. I've updated master and I suspect we'll follow up with changes
to the other release branches.

Thanks for mentioning it.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59251): https://lists.yoctoproject.org/g/yocto/message/59251
Mute This Topic: https://lists.yoctoproject.org/mt/97084127/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] AlmaLinux 8.5 support in Langdale

2023-02-20 Thread Chaplin, Kris via lists.yoctoproject.org


Hello,

I'm working with our team to test supported development OS for our 
AMD/Xilinx PetaLinux distribution built on top of Langdale. The official 
supported Linux distributions are Ubuntu, Fedora, AlmaLinux, Debian and 
OpenSUSE, so we regtest our flow on each of these prior to advertising 
support.


However, the supported version of AlmaLinux for Langdale is 8.5, and 
this is not available for download any more 
(https://mirrors.almalinux.org/isos.html).  The earliest version is 8.6, 
with 8.7 being most current.  The 8.5 isos are stripped from the 
mirrors, so url-games dont work here either.


What is the recommended verison of AlmaLinux to test against Langdale?  
Is there a plan to update the Yocto release notes to reflect this?


Many thanks
Kris





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59250): https://lists.yoctoproject.org/g/yocto/message/59250
Mute This Topic: https://lists.yoctoproject.org/mt/97084127/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] fltk recipe fails

2023-02-20 Thread Takayasu Ito


Hi Ron

The patch file can be found at
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/fltk/fltk


On 2023/02/20 16:51, Mistyron wrote:

Hi,

I need too build fltk but the recipe from openembedded 
(http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/fltk/fltk.bb?h=master) requires a patch file that I could not find. Hence I built my own recipe which looks something like:

[fltk.bb]
SUMMARY = "Fast Light Toolkit (FLTK) is a cross-platform GUI development 
library."
DESCRIPTION = "FLTK provides modern GUI functionality without the bloat 
and supports 3D graphics via OpenGL and its built-in GLUT emulation."


LICENSE = "LGPLv2.1+"
LIC_FILES_CHKSUM = "file://COPYING;md5=353c9fd4163eef6500f7e057aed0b083"

SRCREV = "master"
SRC_URI = "git://github.com/fltk/fltk.git;branch=${SRCREV}"

S = "${WORKDIR}/git"

inherit autotools

do_configure_prepend() {
     ${WORKDIR}/git/autogen.sh
}
[/fltk.bb]

I'm running into an issue with autoge.sh tho, the script appears simple:
[autogen.sh]
#! /bin/sh
#
# This file is no longer referred to in the documentation, it's kept
# for backwards compatibility only.
#
# Just run `autoconf` instead to generate `configure` and you're done.
#
# The old README.Unix.txt stated that it should be executed from within
# the "FLTK source-code directory", hence changing directories is not
# useful and would break if the user's home directory contained spaces.
# Changing directories has been removed in FLTK 1.4.0 and this file
# has been simplified substantially.
#
# Instead of executing it as documented in pre-1.4 README files the new docs
# instruct to just execute `autoconf` which is sufficient and equivalent to
# the old instructions.

autoconf --force || exit 1

test -n "$NOCONFIGURE" || ./configure "$@"
[/autogen.sh]

However, when I attempt to build my image, I get something like:
DEBUG: Executing shell function do_configure
autoconf: error: no input file
WARNING: exit code 1 from a shell command.
ERROR: Execution of 
'/home/yocto/rzg_vlp_v3.0.0/build/tmp/work/aarch64-poky-linux/fltk/1.0-r0/temp/run.do_configure.242968' failed with exit code 1


The autoconf man page states:

"-f, --force
consider all files obsolete"
i.e. I would expect it to work w/o any input files. What am I missing 
and how can I get fltk built succesfully?









--
Takayasu Ito
Yocto Project Ambassador
Solution Department Lineo Solutions, Inc.
https://www.lineo.co.jp/english/
Email: i...@lineo.co.jp


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59249): https://lists.yoctoproject.org/g/yocto/message/59249
Mute This Topic: https://lists.yoctoproject.org/mt/97082226/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] trying to install files when those files already exist

[yocto] trying to install files when those files already exist

Re: [yocto] fltk recipe fails

[yocto] Asking for advice on how to establish license compliance

[yocto] M+ & H bugs with Milestone Movements WW07

[yocto] Enhancements/Bugs closed WW07!

[yocto] Current high bug count owners for Yocto Project 4.2

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

Re: [yocto] Can I specify a prebuilt version of toolchain only for kernel building?

[yocto] Can I specify a prebuilt version of toolchain only for kernel building?

Re: [yocto] AlmaLinux 8.5 support in Langdale

Re: [yocto] AlmaLinux 8.5 support in Langdale

Re: [yocto] AlmaLinux 8.5 support in Langdale

Re: [yocto] AlmaLinux 8.5 support in Langdale

[yocto] AlmaLinux 8.5 support in Langdale

Re: [yocto] fltk recipe fails

16 matches

Site Navigation

Mail list logo

Footer information