From: "Sheng Yang" <styang@fastmail.com>
To: "Alan Third" <alan@idiocy.org>,
"Stephen Berman" <stephen.berman@gmx.net>
Cc: 44065@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#44065: 28.0.50; SVG image not shown completely
Date: Mon, 19 Oct 2020 17:34:45 -0500 [thread overview]
Message-ID: <4fb6f68a-a692-4fb6-9046-516727d8621b@www.fastmail.com> (raw)
In-Reply-To: <20201019204313.GF1166@breton.holly.idiocy.org>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
> I've got something that works for me. I'm using 2.50, so I'd
> appreciate it if someone using 2.45 or below could check that it
> builds and isn't completely broken.
I checked the patch on Debian 10.6, with librsvg2 2.44.10-2.1. Compilation failed with the following error (path sanitized)
/usr/bin/ld: image.o: in function `svg_load_image':
emacs/src/image.c:9810: undefined reference to `rsvg_handle_set_stylesheet'
/usr/bin/ld: emacs/src/image.c:9924: undefined reference to `rsvg_handle_set_stylesheet'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:651：temacs] error 1
make[1]: leaving directory “emacs/src”
make: *** [Makefile:424：src] error 2
BTW, the patch fixes the problem on Arch Linux, with librsvg 2:2.50.1-1.
Sheng Yang(杨圣), PhD candidate
Computer Science Department
University of Maryland, College Park
E-mail: styang@fastmail.com
E-mail (old but still used): yangsheng6810@gmail.com
[-- Attachment #2: Type: text/html, Size: 1573 bytes --]
next prev parent reply other threads:[~2020-10-19 22:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 23:27 bug#44065: 28.0.50; SVG image not shown completely styang
2020-10-18 15:17 ` Eli Zaretskii
2020-10-18 16:02 ` Sheng Yang
2020-10-18 16:13 ` Eli Zaretskii
2020-10-18 16:24 ` Lars Ingebrigtsen
2020-10-18 17:03 ` Eli Zaretskii
2020-10-18 17:42 ` Stephen Berman
2020-10-18 17:48 ` Eli Zaretskii
2020-10-18 18:00 ` Stephen Berman
2020-10-18 18:03 ` Eli Zaretskii
2020-10-19 8:43 ` Lars Ingebrigtsen
2020-10-19 9:10 ` Stephen Berman
2020-10-19 20:43 ` Alan Third
2020-10-19 22:34 ` Sheng Yang [this message]
2020-10-20 12:31 ` Alan Third
2020-10-20 17:15 ` Sheng Yang
2020-10-20 19:54 ` Alan Third
2020-10-21 10:54 ` Lars Ingebrigtsen
2020-10-21 15:58 ` Corwin Brust
2020-10-21 16:31 ` Eli Zaretskii
2020-10-21 17:28 ` Sheng Yang
2020-10-21 19:03 ` Alan Third
2020-10-22 11:42 ` Lars Ingebrigtsen
2020-10-22 12:51 ` Eli Zaretskii
2020-10-22 19:11 ` Alan Third
2020-10-19 14:51 ` Eli Zaretskii
2020-10-18 19:18 ` Sheng Yang
2020-10-18 23:13 ` Alan Third
2020-10-23 20:17 ` Andy Moreton
2020-10-24 7:09 ` Eli Zaretskii
2020-10-24 17:01 ` Alan Third
2020-10-24 17:04 ` Eli Zaretskii
2020-10-24 10:43 ` Andy Moreton
2020-10-25 12:26 ` Andy Moreton
2020-10-25 16:25 ` Alan Third
2020-10-25 17:12 ` Andy Moreton
2020-10-25 17:27 ` Eli Zaretskii
2020-10-25 23:12 ` Alan Third
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=4fb6f68a-a692-4fb6-9046-516727d8621b@www.fastmail.com \
--to=styang@fastmail.com \
--cc=44065@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=larsi@gnus.org \
--cc=stephen.berman@gmx.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/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).