unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Ugo Tomei" <utomei@tiscali.it>
Cc: luangruo@yahoo.com, 61988@debbugs.gnu.org
Subject: bug#61988: error compiling emacs
Date: Tue, 07 Mar 2023 18:59:58 +0200	[thread overview]
Message-ID: <83edq05wfl.fsf@gnu.org> (raw)
In-Reply-To: <000401d95114$16299540$427cbfc0$@tiscali.it> (utomei@tiscali.it)

> From: "Ugo Tomei" <utomei@tiscali.it>
> Cc: <luangruo@yahoo.com>,
> 	<61988@debbugs.gnu.org>
> Date: Tue, 7 Mar 2023 17:44:26 +0100
> 
> In the emacs dir I see config.log:
> 
> configure:14159: checking for libwebpdemux >= 0.6.0
> configure:14323: gcc -o conftest  -g3 -O2 -pthread -isystem
> /usr/include/librsvg-2.0 -isystem /usr/include/gdk-pixbuf-2.0 -isystem
> /usr/include/x86_64-linux-gnu -isystem /usr/include/libmount -isystem
> /usr/include/blkid -isystem /usr/include/cairo -isystem
> /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include
> -isystem /usr/include/pixman-1 -isystem /usr/include/uuid -isystem
> /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem
> /usr/include/webp       conftest.c -lsqlite3  -lsqlite3 -lX11   >&5
> | #define HAVE_WEBP 1
> pkg_cv_WEBP_CFLAGS=-I/usr/include/webp
> WEBP_CFLAGS='-isystem /usr/include/webp'
> WEBP_LIBS='-lwebpdemux'
> 
> I attached the log.
> [...]
> configure:14159: checking for libwebpdemux >= 0.6.0
> configure:14166: $PKG_CONFIG --exists --print-errors "$WEBP_MODULE"
> configure:14169: $? = 0
> configure:14183: $PKG_CONFIG --exists --print-errors "$WEBP_MODULE"
> configure:14186: $? = 0
> configure:14224: result: yes

I'm stumped: why doesn't it test WebPGetInfo?  Po Lu, do you
understand what happened here?





  reply	other threads:[~2023-03-07 16:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 11:23 bug#61988: error compiling emacs Ugo Tomei
2023-03-05 19:41 ` Eli Zaretskii
2023-03-06  9:10   ` Ugo Tomei
2023-03-06  0:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-06  9:38   ` Ugo Tomei
2023-03-06 10:35     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-06 12:08       ` Eli Zaretskii
2023-03-06 13:43         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-06 15:38           ` Eli Zaretskii
2023-03-07  0:34             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07  3:38               ` Eli Zaretskii
2023-03-07  5:03                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 13:00                   ` Eli Zaretskii
2023-03-07 13:36                     ` bug#61988: R: " Ugo Tomei
2023-03-07 14:11                       ` Eli Zaretskii
2023-03-07 14:34                         ` bug#61988: R: " Ugo Tomei
2023-03-07 15:27                           ` Eli Zaretskii
2023-03-07 16:21                             ` Eli Zaretskii
2023-03-07 16:44                         ` bug#61988: R: " Ugo Tomei
2023-03-07 16:59                           ` Eli Zaretskii [this message]
2023-03-08  0:09                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08  8:32                               ` Ugo Tomei
2023-03-08  9:02                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08  9:44                                   ` Ugo Tomei
2023-03-08 10:42                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08 12:26                                       ` Ugo Tomei
2023-03-08 12:55                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08 14:24                                           ` Eli Zaretskii
2023-09-06  0:01                                             ` Stefan Kangas

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=83edq05wfl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61988@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=utomei@tiscali.it \
    /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).