All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] librsvg: update 2.58.2 -> 2.59.2
Date: Thu, 12 Dec 2024 13:45:14 +0000	[thread overview]
Message-ID: <509DAE26-9961-4082-96EB-E6F2F8411D2F@arm.com> (raw)
In-Reply-To: <20241204120838.141829-1-alex.kanavin@gmail.com>

On 4 Dec 2024, at 12:08, Alexander Kanavin via lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org> wrote:
> +export EXTRA_NATIVE_PKGCONFIG_PATH = "${B}/meson-uninstalled:"
> +LDFLAGS += " -L${B}/rsvg"
> +# needed on ubuntu 20.04/debian 11 to avoid 'undefined reference to `dlsym'' errors
> +BUILD_LDFLAGS += " -ldl"

That’s a big pile of yuck, some of which feels like “how does this work upstream?” levels of breakage.  Are we exposing flaws in the librsvg build, or our meson integration, or something else?

> +SYSROOT_PREPROCESS_FUNCS:append:class-target = " pkgconfig_sysroot_preprocess"
> +
> +# installed .pc file contains
> +# prefix=${pcfiledir}/../..
> +# which is expanded to an absolute path, and thus doesn't work when additionally prefixed with a sysroot directory
> +pkgconfig_sysroot_preprocess() {
> +        sed -i -e "s:^prefix=.*:prefix=${prefix}:g" ${SYSROOT_DESTDIR}${libdir}/pkgconfig/librsvg-2.0.pc
> +}

Surely a better fix is to upstream a change to set the prefix to the prefix?

Ross

  parent reply	other threads:[~2024-12-12 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 12:08 [PATCH] librsvg: update 2.58.2 -> 2.59.2 Alexander Kanavin
2024-12-05  9:39 ` [OE-core] " Mathieu Dubois-Briand
2024-12-05 10:06   ` Alexander Kanavin
2024-12-05 14:20     ` Mathieu Dubois-Briand
2024-12-12 13:45 ` Ross Burton [this message]
2024-12-12 13:59   ` Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=509DAE26-9961-4082-96EB-E6F2F8411D2F@arm.com \
    --to=ross.burton@arm.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.