unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Core updates status
Date: Fri, 26 Apr 2024 13:56:12 +0100	[thread overview]
Message-ID: <4qoo3nfwivyjoqduswls7tptq5z2e2pz5xwogdvubxz7kmr4si@xaxu5sqskgl6> (raw)
In-Reply-To: <Y3ZbdsXSrNZ2620EIWcH1sdV8Kac5icBl95Ghw8dpysffldThOTNmjO2JXJGpbDRDAR1Rel1Um5epfaZKWnAIVneuJf2OpbQRIuWt5iZQl0=@protonmail.com>

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.

Steve / Futurile



  reply	other threads:[~2024-04-26 12:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  6:08 Core updates status Steve George
2024-04-24  9:56 ` Christina O'Donnell
2024-04-24 13:17   ` Steve George
2024-04-24 14:21     ` Christina O'Donnell
2024-04-25 14:06     ` Christina O'Donnell
2024-04-25 14:06       ` bug#40316: " Christina O'Donnell
2024-04-25 17:01       ` nss not reproducible Christina O'Donnell
2024-04-25 18:45 ` Core updates status Kaelyn
2024-04-26 12:56   ` Steve George [this message]
2024-04-26 15:58     ` Efraim Flashner
2024-05-05 20:45       ` Josselin Poiret
2024-05-06  2:38         ` Maxim Cournoyer
2024-05-06  8:47           ` Josselin Poiret
2024-05-06 10:21             ` Ludovic Courtès
2024-05-08  9:03               ` Josselin Poiret
2024-05-08 21:42                 ` [PATCH] gnu: glibc: Update patches following upstream's master branch Josselin Poiret
2024-05-14  9:22                   ` Ludovic Courtès
2024-05-09 15:41                 ` Core updates status Maxim Cournoyer
2024-05-13  8:49                 ` Efraim Flashner
2024-05-08 10:05             ` Andreas Enge
2024-05-08 17:46               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-05-09 15:38               ` Maxim Cournoyer
2024-05-10  8:08                 ` Andreas Enge
2024-05-13  8:51                 ` Efraim Flashner

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=4qoo3nfwivyjoqduswls7tptq5z2e2pz5xwogdvubxz7kmr4si@xaxu5sqskgl6 \
    --to=steve@futurile.net \
    --cc=guix-devel@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).