From: Jim Myhrberg <jimehgeek@gmail.com>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs master build broken [GNU/Linux?]
Date: Tue, 3 Dec 2024 02:30:01 +0000 [thread overview]
Message-ID: <CAGaZ61u6TOvVSL99Hb5ChojNP-iE=L1W3cNt+fnQDfhZjn9MhA@mail.gmail.com> (raw)
In-Reply-To: <CAGaZ61sWv=ZuK3ENKTa6rTVNZ8YTMTHfOauAY=p1BN2yV4Syfg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 154 bytes --]
Commit f65de1019dca6398097751abefcad7e1a4637551 on the emacs-30 branch
fixes the issue. Seems the change was meant for librsvg 2.59.x rather than
2.58.x.
[-- Attachment #2: Type: text/html, Size: 179 bytes --]
next prev parent reply other threads:[~2024-12-03 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 22:42 Emacs master build broken [GNU/Linux?] Angelo Graziosi
2024-12-02 23:34 ` Jim Myhrberg
2024-12-03 2:30 ` Jim Myhrberg [this message]
2024-12-03 3:28 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGaZ61u6TOvVSL99Hb5ChojNP-iE=L1W3cNt+fnQDfhZjn9MhA@mail.gmail.com' \
--to=jimehgeek@gmail.com \
--cc=angelo.g0@libero.it \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).