From: Eli Zaretskii <eliz@gnu.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: grgoffe@yahoo.com, 18552@debbugs.gnu.org
Subject: bug#18552: Possible bug building emacs trunk with Fedora 19-x86_64
Date: Thu, 25 Sep 2014 12:48:55 +0300 [thread overview]
Message-ID: <834mvwvxmg.fsf@gnu.org> (raw)
In-Reply-To: <5423DDA2.1010603@swipnet.se>
> Date: Thu, 25 Sep 2014 11:17:22 +0200
> From: "Jan D." <jan.h.d@swipnet.se>
> Cc: 18552@debbugs.gnu.org
>
> George R Goffe skrev 2014-09-25 10:26:
> > Jan,
> >
> > The short answer is no. I installed libjpeg-9a and it's jconfig.h has NO version string. A bug?
>
> No, they just moved it to libjpeg.h:
I think you mean jpeglib.h.
> #define JPEG_LIB_VERSION 90 /* Compatibility version 9.0 */
>
> Is there some reason you need libjpeg-9a? It seems there is confusion
> about which version of jpeg configure picks up.
>
> On the other hand, Emacs should work with jpeg 90 also.
It does for me (with libjpeg-9a).
next prev parent reply other threads:[~2014-09-25 9:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 21:42 bug#18552: Possible bug building emacs trunk with Fedora 19-x86_64 George R Goffe
2014-09-24 22:21 ` Glenn Morris
2014-09-24 23:38 ` George R Goffe
2014-09-25 3:49 ` Dmitry Antipov
2014-09-25 5:03 ` George R Goffe
2014-09-25 6:29 ` Jan Djärv
[not found] ` <1411633577.97603.YahooMailNeo@web162105.mail.bf1.yahoo.com>
2014-09-25 9:17 ` Jan D.
2014-09-25 9:48 ` Eli Zaretskii [this message]
2014-09-25 9:56 ` Jan D.
2014-10-01 18:13 ` Glenn Morris
2014-10-01 18:20 ` Jan Djärv
2014-10-01 22:05 ` George R Goffe
2014-10-01 18:25 ` Eli Zaretskii
2014-10-01 22:24 ` George R Goffe
2014-10-01 22:38 ` Glenn Morris
2014-10-02 0:17 ` George R Goffe
2014-10-02 1:27 ` George R Goffe
2014-10-02 1:47 ` Glenn Morris
2014-10-02 1:58 ` George R Goffe
2014-10-05 6:19 ` Glenn Morris
2014-10-05 7:32 ` George R Goffe
2014-10-05 16:49 ` George R Goffe
2014-09-25 5:36 ` George R Goffe
2014-09-25 8:24 ` Dmitry Antipov
2014-09-25 9:03 ` George R Goffe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834mvwvxmg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18552@debbugs.gnu.org \
--cc=grgoffe@yahoo.com \
--cc=jan.h.d@swipnet.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.