From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Steve George <steve@futurile.net>,
Josselin Poiret <dev@jpoiret.xyz>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: Status of ‘core-updates’
Date: Fri, 19 Apr 2024 11:22:56 -0400 [thread overview]
Message-ID: <87msppl6lr.fsf@gmail.com> (raw)
In-Reply-To: <87o7a5fnkg.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 19 Apr 2024 16:13:03 +0200")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Since branches were merged in, I believe the problem we are facing at
>> the moment is librsvg failing its test suite with a segfault (!). Could
>> be the glibc upgrade, or rust itself, I'm not sure. I was trying to
>> upgrade librsvg, which needs an update anyway, but it pulls many rust
>> crates updates. I'll get there eventually, if nobody beats me to it.
>
> Ouch, OK. I guess it doesn’t hurt if several of us take a look and we
> share our findings here.
>
>>> Josselin, Maxim: could you explain what problems there are around
>>> pkgconf and what you would recommend?
>>
>> Nothing in particular to point at the moment, but remaining problems
>> would manifest in the form of missing inputs, due to transitive libtool
>> dependencies causing overlinking and the new pkgconf being smart enough
>> to optimize away some previously captured link directives that would be
>> baked in the RUNPATH and sastify libtool overlinking needs.
>>
>> The solution is to hunt the libtool .la files from the transitive
>> dependencies causing the problem and removing them. See commit
>> b6540bd285cbe5920ad379ddfc6256359ee7204c for an example.
>
> Good. So it seems like we can move forward after all and just do the
> “normal” job and finding and fixing build failures along these lines.
>
> Do we need ci.guix to build more packages to facilitate testing and
> debugging? That’s something I can help with (though I’ll be away for a
> week).
If we do this, and I believe it'd be useful, I think it'd help to fork a
'core-updates-frozen' and have the CI rebuild this one fully, leaving
'core-updates' open to business as usual.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-04-19 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 11:21 Status of ‘core-updates’ Ludovic Courtès
2024-03-30 10:55 ` Josselin Poiret
2024-04-10 14:39 ` Ludovic Courtès
2024-04-11 10:18 ` Steve George
2024-04-12 20:21 ` Ludovic Courtès
2024-04-17 17:47 ` Maxim Cournoyer
2024-04-17 22:52 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-04-19 14:13 ` Ludovic Courtès
2024-04-19 15:22 ` Maxim Cournoyer [this message]
2024-04-22 16:20 ` Efraim Flashner
2024-04-20 11:14 ` Christopher Baines
2024-04-20 21:15 ` Maxim Cournoyer
2024-05-02 7:53 ` bug#70456: Request for merging "core-updates" branch Ludovic Courtès
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=87msppl6lr.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=steve@futurile.net \
/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).