From: Petr Hracek <phracek@redhat.com>
To: 20124@debbugs.gnu.org
Subject: bug#20124: Building emacs and libjpeg not found on Fedora 22
Date: Tue, 17 Mar 2015 10:47:10 +0100 [thread overview]
Message-ID: <5507F81E.1070704@redhat.com> (raw)
I am trying to build emacs with following parameters in configuration
script.
./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --program-prefix=
--disable-dependency-tracking --prefix=/usr --exec-prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64
--libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib
--mandir=/usr/share/man --infodir=/usr/share/info --with-dbus --with-gif
--with-jpeg --with-png --with-rsvg --with-tiff --with-xft --with-xpm
--with-x-toolkit=gtk3 --with-gpm=no
It fails with:
configure: error: The following required libraries were not found:
libjpeg
Maybe some development libraries/packages are missing?
If you don't want to link with them give
--with-jpeg=no
as options to configure
I have installed following libjpeg versions:
libjpeg-turbo-1.4.0-1.fc22
libjpeg-turbo-devel-1.4.0-1.fc22.
(http://koji.fedoraproject.org/koji/buildinfo?buildID=605282)
The first package delivers SO libraries like so.62.0
second one delivers headers and libjpeg.so library
Do you have any idea where could be a problem?
Greetings
Petr
--
Petr Hracek
Software Engineer
Developer Experience
Red Hat, Inc
Mob: +420777056169
email: phracek@redhat.com
next reply other threads:[~2015-03-17 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 9:47 Petr Hracek [this message]
2015-03-17 9:57 ` bug#20124: Building emacs and libjpeg not found on Fedora 22 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
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=5507F81E.1070704@redhat.com \
--to=phracek@redhat.com \
--cc=20124@debbugs.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).