From: Eli Zaretskii <eliz@gnu.org>
To: sean.sieger@gmail.com
Cc: 7716@debbugs.gnu.org
Subject: bug#7716: 23.2.91; Pretest Windows binary doesn't support PNG images
Date: Sat, 25 Dec 2010 00:24:02 +0200 [thread overview]
Message-ID: <8339pmernh.fsf@gnu.org> (raw)
In-Reply-To: <83r5d7ec4p.fsf@gnu.org>
> Date: Fri, 24 Dec 2010 11:47:02 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: bug-gnu-emacs@gnu.org
>
> > From: Sean Sieger <sean.sieger@gmail.com>
> > Date: Thu, 23 Dec 2010 15:23:21 -0500
> > Cc:
> >
> > (I cannot say it is blissful being as limited as I am.) Sorry I wasn't
> > reading closely ... um, nope, didn't build any differently.
>
> That's strange, because the binary of the previous pretest shows PNG
> images.
I take that back. The precompiled binary from the 23.2.90 pretest on
alpha.gnu.org doesn't display PNG, either.
This is consistent with what Drew sees: none of the precompiled
binaries, including those of Emacs 24 snapshots, can display PNG.
So, Sean, please try to debug this on your machine, because the
binaries I build here don't have that problem. For starters, where
(from what archive of which package) did you get the PNG headers?
next prev parent reply other threads:[~2010-12-24 22:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 6:03 bug#7716: 23.2.91; Pretest Windows binary doesn't support PNG images Eli Zaretskii
2010-12-23 15:29 ` Drew Adams
2010-12-23 16:09 ` Eli Zaretskii
2010-12-23 17:36 ` Drew Adams
2010-12-23 18:23 ` Eli Zaretskii
2010-12-23 21:18 ` Drew Adams
2010-12-23 23:24 ` Sean Sieger
2010-12-24 0:40 ` Drew Adams
2010-12-24 2:56 ` David De La Harpe Golden
2010-12-24 10:03 ` Eli Zaretskii
2010-12-24 9:59 ` Eli Zaretskii
2010-12-24 16:03 ` Drew Adams
2010-12-24 16:23 ` Eli Zaretskii
2010-12-24 16:47 ` Drew Adams
2010-12-24 18:11 ` Eli Zaretskii
2010-12-24 18:21 ` Drew Adams
2010-12-24 18:36 ` Drew Adams
2010-12-24 19:03 ` Eli Zaretskii
2010-12-24 19:21 ` Drew Adams
2010-12-24 19:35 ` Eli Zaretskii
2010-12-24 19:46 ` Drew Adams
2010-12-24 23:52 ` Drew Adams
2011-01-10 22:59 ` Drew Adams
2011-01-11 4:07 ` Eli Zaretskii
2011-01-11 4:41 ` Drew Adams
2011-01-11 18:45 ` Eli Zaretskii
2011-01-11 19:19 ` Drew Adams
2011-01-11 19:31 ` Eli Zaretskii
2011-01-11 19:53 ` Drew Adams
2011-01-11 21:02 ` Lennart Borgman
2010-12-24 18:21 ` Sean Sieger
2010-12-24 19:01 ` Eli Zaretskii
2010-12-23 18:51 ` Sean Sieger
2010-12-23 18:37 ` Sean Sieger
2010-12-23 18:57 ` Sean Sieger
2010-12-23 18:58 ` Eli Zaretskii
2010-12-23 20:23 ` Sean Sieger
2010-12-24 9:47 ` Eli Zaretskii
2010-12-24 22:24 ` Eli Zaretskii [this message]
2010-12-24 22:56 ` Sean Sieger
2010-12-25 9:19 ` Eli Zaretskii
2010-12-25 10:58 ` Sean Sieger
2010-12-25 12:57 ` Eli Zaretskii
2010-12-29 18:05 ` Eli Zaretskii
2010-12-29 20:12 ` Sean Sieger
2010-12-29 23:57 ` Jason Rumney
2010-12-30 4:12 ` Eli Zaretskii
2010-12-30 15:58 ` Jason Rumney
2010-12-31 12:46 ` 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=8339pmernh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7716@debbugs.gnu.org \
--cc=sean.sieger@gmail.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/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).