From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: grgoffe@yahoo.com, 18552@debbugs.gnu.org
Subject: bug#18552: Possible bug building emacs trunk with Fedora 19-x86_64
Date: Wed, 01 Oct 2014 21:25:33 +0300 [thread overview]
Message-ID: <834mvnk5pe.fsf@gnu.org> (raw)
In-Reply-To: <8x1tqrvetn.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, grgoffe@yahoo.com, 18552@debbugs.gnu.org
> Date: Wed, 01 Oct 2014 14:13:08 -0400
>
>
> So was any conclusion reached here?
I tend to think the OP's system is misconfigured. 32-bit vs 64-bit
messup is one possibility.
Another way to continue investigating this is for the OP to try
compiling a short test program that includes the JPEG header, and see
if it compiles, and if not, what warning/error messages appear. The
log the OP sent says just
configure:12340: WARNING: libjpeg found, but not version 6b or later
which isn't very informative.
next prev parent reply other threads:[~2014-10-01 18:25 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
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 [this message]
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
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=834mvnk5pe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18552@debbugs.gnu.org \
--cc=grgoffe@yahoo.com \
--cc=rgm@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).