* [OE-core][master][PATCH v2] librsvg: Fix do_package_qa error for librsvg
@ 2024-03-08 5:03 Nikhil R
2024-03-08 7:01 ` Alexander Kanavin
0 siblings, 1 reply; 4+ messages in thread
From: Nikhil R @ 2024-03-08 5:03 UTC (permalink / raw)
To: openembedded-core, nikhilar2410; +Cc: ranjitsinh.rathod, Nikhil R
When using meta-rust layer for rust below
do_package_qa error in librsvg is observed
Fix the below error:
ERROR: librsvg-2.52.10-r0 do_package_qa: QA Issue: File /usr/bin/rsvg-convert in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) File /usr/bin/rsvg-convert in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags] ERROR: librsvg-2.52.10-r0 do_package_qa: Fatal QA errors were found, failing task.
Signed-off-by: Nikhil R <nikhil.r@kpit.com>
---
meta/recipes-gnome/librsvg/librsvg_2.56.3.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb b/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb
index 9824b8898d..e6eece6858 100644
--- a/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb
+++ b/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb
@@ -77,3 +77,5 @@ FILES:librsvg-gtk = "${libdir}/gdk-pixbuf-2.0/*/*/*.so \
RRECOMMENDS:librsvg-gtk = "gdk-pixbuf-bin"
PIXBUF_PACKAGES = "librsvg-gtk"
+
+TARGET_CC_ARCH += "${LDFLAGS}"
--
2.25.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [OE-core][master][PATCH v2] librsvg: Fix do_package_qa error for librsvg
2024-03-08 5:03 [OE-core][master][PATCH v2] librsvg: Fix do_package_qa error for librsvg Nikhil R
@ 2024-03-08 7:01 ` Alexander Kanavin
2024-03-11 12:15 ` [master][PATCH " Nisha.M.Parrakat
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Kanavin @ 2024-03-08 7:01 UTC (permalink / raw)
To: nikhil; +Cc: openembedded-core, ranjitsinh.rathod, Nikhil R
meta-rust is generally seen as obsolete, is there a particular reason
you need to use it with oe-core master, instead of the standard rust
recipes?
Even then, this looks like it needs to be fixed in meta-rust, rather
than individual recipes. The error does not occur with official rust
toolchain, so meta-rust should just copy what that does.
Alex
On Fri, 8 Mar 2024 at 06:03, nikhil <nikhilar2410@gmail.com> wrote:
>
> When using meta-rust layer for rust below
> do_package_qa error in librsvg is observed
>
> Fix the below error:
> ERROR: librsvg-2.52.10-r0 do_package_qa: QA Issue: File /usr/bin/rsvg-convert in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) File /usr/bin/rsvg-convert in package rsvg doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags] ERROR: librsvg-2.52.10-r0 do_package_qa: Fatal QA errors were found, failing task.
>
> Signed-off-by: Nikhil R <nikhil.r@kpit.com>
> ---
> meta/recipes-gnome/librsvg/librsvg_2.56.3.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb b/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb
> index 9824b8898d..e6eece6858 100644
> --- a/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb
> +++ b/meta/recipes-gnome/librsvg/librsvg_2.56.3.bb
> @@ -77,3 +77,5 @@ FILES:librsvg-gtk = "${libdir}/gdk-pixbuf-2.0/*/*/*.so \
> RRECOMMENDS:librsvg-gtk = "gdk-pixbuf-bin"
>
> PIXBUF_PACKAGES = "librsvg-gtk"
> +
> +TARGET_CC_ARCH += "${LDFLAGS}"
> --
> 2.25.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#196846): https://lists.openembedded.org/g/openembedded-core/message/196846
> Mute This Topic: https://lists.openembedded.org/mt/104803790/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [master][PATCH v2] librsvg: Fix do_package_qa error for librsvg
2024-03-08 7:01 ` Alexander Kanavin
@ 2024-03-11 12:15 ` Nisha.M.Parrakat
2024-03-11 13:00 ` [OE-core] " Alexander Kanavin
0 siblings, 1 reply; 4+ messages in thread
From: Nisha.M.Parrakat @ 2024-03-11 12:15 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Thanks Alex for the reply.
So till now we are using meta-rust master along with the kirkstone yocto layers and are trying to understand if it makes sense to use it further.
We had a few questions for the maintainence of Rust.
1. Can we say, that oe-core will support Rust in future after Kirkstone as a standalone (without any external dependency )?
2. We assume that kirkstone will stay with 1.59 and those who want later versions (1.68+)can use meta-lts-mixins
3. We have the following assumptions for meta-lts-mixins
a) We see kirkstone/rust-1.68, kirkstone/rust-1.70 branches.
A new branch will be created for a newer and stable rust version for example kirkstone/rust-1.75 .
b) If *1* is not correct then we assume meta-lts-mixins will cater to all the LTS layers in future. That means we may see branches like scarthgap/rust-***
Thanks in advance for your reply !
regards,
Nisha Parrakat
[-- Attachment #2: Type: text/html, Size: 1599 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [OE-core] [master][PATCH v2] librsvg: Fix do_package_qa error for librsvg
2024-03-11 12:15 ` [master][PATCH " Nisha.M.Parrakat
@ 2024-03-11 13:00 ` Alexander Kanavin
0 siblings, 0 replies; 4+ messages in thread
From: Alexander Kanavin @ 2024-03-11 13:00 UTC (permalink / raw)
To: Nisha.M.Parrakat; +Cc: openembedded-core
On Mon, 11 Mar 2024 at 13:15, <Nisha.M.Parrakat@bmw.de> wrote:
> 1. Can we say, that oe-core will support Rust in future after Kirkstone as a standalone (without any external dependency )?
Yes. Rust is now part of the core, and will stay there.
> 2. We assume that kirkstone will stay with 1.59 and those who want later versions (1.68+)can use meta-lts-mixins
That's right.
> 3. We have the following assumptions for meta-lts-mixins
>
> a) We see kirkstone/rust-1.68, kirkstone/rust-1.70 branches.
> A new branch will be created for a newer and stable rust version for example kirkstone/rust-1.75 .
There's also kirkstone/rust which is not tied to a specific rust
version and aims to provide the 'latest'.
> b) If 1 is not correct then we assume meta-lts-mixins will cater to all the LTS layers in future. That means we may see branches like scarthgap/rust-***
That will not necessarily happen. It depends on somebody willing to do
the work. But this also means that you can make that contribution.
There are typically two steps:
1. Update master to the needed upstream rust release.
2. Backport those recipes into a branch in meta-lts-mixins.
Keep in mind that this is a community project, and no one owes you
these things. The good news is that you are welcome to handle them and
share with the community.
Alex
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-03-11 13:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-08 5:03 [OE-core][master][PATCH v2] librsvg: Fix do_package_qa error for librsvg Nikhil R
2024-03-08 7:01 ` Alexander Kanavin
2024-03-11 12:15 ` [master][PATCH " Nisha.M.Parrakat
2024-03-11 13:00 ` [OE-core] " Alexander Kanavin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.