From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, Alexander Kuleshov <kuleshovmail@gmail.com>
Subject: Re: [PATCH] Fix compilation erorr when --enable-gcc-warnings passed
Date: Sun, 24 Jan 2016 13:34:59 +0600 [thread overview]
Message-ID: <20160124073459.GA29099@localhost> (raw)
In-Reply-To: <56A41F7F.4040404@cs.ucla.edu>
On 01-23-16, Paul Eggert wrote:
> Alexander Kuleshov wrote:
> >I can't reproduce your crash. The png image displaying
> >perfectly.
>
> I suspect the bug is now masked because lookup_rgb_color now throws a signal
> under Cairo. I followed up at:
>
> http://bugs.gnu.org/22442#20
Hello,
Even without it I can't reproduce this bug. I've checkout to the previous
commit (035bd8159fe5bcea15eacc8a23ab54f4bc3b6f17) and configured and
built emacs with:
./configure --enable-link-time-optimization --without-pop \
--without-kerberos --without-kerberos5 --without-hesiod \
--with-sound=alsa --with-x-toolkit=gtk3 --with-xpm --with-jpeg \
--with-tiff --with-gif --with-png --with-rsvg --with-cairo \
--with-xml2 --with-imagemagick --with-xft --without-libotf \
--with-xim --with-xaw3d --with-dbus --without-gconf \
--without-gsettings --without-selinux --with-gnutls --with-zlib \
--with-modules --with-file-notification=inotify --without-makeinfo \
--with-x && make
Than I've opened image as you described in the http://bugs.gnu.org/22442
and it works perfectly for me.
prev parent reply other threads:[~2016-01-24 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 10:54 [PATCH] Fix compilation erorr when --enable-gcc-warnings passed Alexander Kuleshov
2016-01-23 0:06 ` Paul Eggert
2016-01-23 6:28 ` Alexander Kuleshov
2016-01-23 9:08 ` Paul Eggert
2016-01-23 9:23 ` Eli Zaretskii
2016-01-23 9:41 ` Paul Eggert
2016-01-23 11:57 ` Alexander Kuleshov
2016-01-23 12:04 ` Alexander Kuleshov
2016-01-23 12:37 ` Alexander Kuleshov
2016-01-24 0:49 ` Paul Eggert
2016-01-24 7:34 ` Alexander Kuleshov [this message]
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=20160124073459.GA29099@localhost \
--to=kuleshovmail@gmail.com \
--cc=eggert@cs.ucla.edu \
--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).