From: Petr Hracek <phracek@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20124@debbugs.gnu.org
Subject: bug#20124: Building emacs and libjpeg not found on Fedora 22
Date: Wed, 18 Mar 2015 13:29:35 +0100 [thread overview]
Message-ID: <55096FAF.4010300@redhat.com> (raw)
In-Reply-To: <83vbhzyf3z.fsf@gnu.org>
On 03/17/2015 01:37 PM, Eli Zaretskii wrote:
>> Date: Tue, 17 Mar 2015 12:35:23 +0100
>> From: Petr Hracek<phracek@redhat.com>
>> CC:20124@debbugs.gnu.org
>>
>> configure:13903: $? = 0
>> configure:13912: result: yes
>> *configure:13937: WARNING: libjpeg found, but not version 6b or later*
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Isn't the above self-explanatory?
>
> the configure script looks at the value of JPEG_LIB_VERSION it finds
> in jpeglib.h header file, so I'm guessing either your libjpeg
> installation is too old, or you have an old jpeglib.h header somewhere
> where the compiler picks it ahead of the correct one.
I know that it is self-explanatory but my jpeglib.h header file has
JPEG_LIB_VERSION = 62.
No I don't have neither jpeglib.h nor libjpeg-turbo package old.
But I am going to find if there could not be a problem with emacs
configure script.
Several times there is mentioned conftest.$ac. I am going to test it.
I think that emacs configure scripts does not work well some times.
--
Petr Hracek
Software Engineer
Developer Experience
Red Hat, Inc
Mob: +420777056169
email:phracek@redhat.com
next prev parent reply other threads:[~2015-03-18 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 9:47 bug#20124: Building emacs and libjpeg not found on Fedora 22 Petr Hracek
2015-03-17 9:57 ` Petr Hracek
2015-03-17 11:02 ` Eli Zaretskii
2015-03-17 11:35 ` Petr Hracek
2015-03-17 12:37 ` Eli Zaretskii
2015-03-18 12:29 ` Petr Hracek [this message]
2015-03-18 6:41 ` Paul Eggert
2015-03-18 6:48 ` Glenn Morris
2015-03-23 7:24 ` Paul Eggert
2015-03-23 16:18 ` Glenn Morris
2015-03-23 17:37 ` Paul Eggert
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=55096FAF.4010300@redhat.com \
--to=phracek@redhat.com \
--cc=20124@debbugs.gnu.org \
--cc=eliz@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).