[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Core updates status
From: |
Efraim Flashner |
Subject: |
Re: Core updates status |
Date: |
Fri, 26 Apr 2024 18:58:55 +0300 |
On Fri, Apr 26, 2024 at 01:56:12PM +0100, Steve George wrote:
> Hi,
>
> On 25 Apr, Kaelyn wrote:
> > Hi,
> >
> > On Tuesday, April 23rd, 2024 at 11:08 PM, Steve George <steve@futurile.net>
> > wrote:
> (...)
> > > - guile-rsvg failing
> > > - https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70537
> > > - I'm able to build librsvg@2.56.4 but not guile-rsvg
> > > - guile-rsvg@2.18.1 / guile2.2-rsvg
> > > - guile-rsvg builds on master - connected?
> >
> > I've started looking at this build failure this morning, and my initial
> > impressions are that a propagated-input is missing. I tried building
> > guile-rsvg from core-updates and the build failed with three missing pango
> > libraries (ld could not find -lpangocairo-1.0, -lpangoft2-1.0, and
> > -lpango-1.0). I tried moving pango from the inputs to the propagated-inputs
> > for librsvg, and that fixed the build of guile-rsvg. I'm just not sure if
> > that is the right place to propagate it; I haven't yet traced where the
> > pango libraries are being added to the linking command, as I've checked the
> > pkgconfig files for librsvg, cairo, and a couple of other packages and not
> > seen references to pango (which is what makes me think the pango
> > propagated-input is needed elsewhere, and not actually in librsvg--but I
> > also don't know Rust or what dependencies the rust code in librsvg has).
>
> That's great, thanks for taking a look. Efraim mentioned that there would be
> Rust changes for it.
Seeing that librsvg has rust-pango (and some others) in cargo-inputs,
and therefore needs pango to build, I think it's safe to move pango (and
others as needed) to propagated inputs. Make sure to make the necessary
changes to librsvg-2.40 also.
I haven't had any problems building the rust based librsvg on
core-updates, so I'd suggest leaving that alone for now.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature