all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: Ubuntu 16.04 cannot compile commit c4687d920db081f29e93cca8156793d545a827e2
Date: Fri, 24 Jan 2020 00:47:28 -0800	[thread overview]
Message-ID: <5e8c8262-8333-d17a-e21a-454b7cc7f780@cs.ucla.edu> (raw)
In-Reply-To: <878slyexyy.fsf@mat.ucm.es>

On 1/23/20 12:09 PM, Uwe Brauer wrote:
> So png12 is missing, why did compile me tell about it?

I guess your pkg-config claimed that you have a working libpng, even though you 
don't. Try running the following shell commands:

pkg-config --cflags "libpng >= 1.0.0"
pkg-config --libs "libpng >= 1.0.0"

If these commands tell 'configure' to use flags like -lpng12 but those flags 
don't work, then you have a problem with your pkg-config installation somewhere.

Although you can work around the problem by building Emacs with './configure 
--without-png', it's better to get your png installation whipped into shape.



  reply	other threads:[~2020-01-24  8:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 20:09 Ubuntu 16.04 cannot compile commit c4687d920db081f29e93cca8156793d545a827e2 Uwe Brauer
2020-01-24  8:47 ` Paul Eggert [this message]
2020-01-24  8:52   ` Uwe Brauer
2020-01-24  9:20     ` Robert Pluim
2020-01-24  9:29     ` Paul Eggert
2020-01-24 10:21       ` Uwe Brauer
2020-01-24 13:28         ` Eli Zaretskii
2020-01-24 14:28         ` Stefan Monnier
2020-01-24 16:18           ` Uwe Brauer
2020-01-25 22:20           ` Uwe Brauer
2020-01-25 22:48             ` Stefan Monnier
2020-01-26  8:01             ` Paul Eggert
2020-01-26  8:42               ` [SOLVED (sort of)] (was: Ubuntu 16.04 cannot compile commit c4687d920db081f29e93cca8156793d545a827e2) Uwe Brauer

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=5e8c8262-8333-d17a-e21a-454b7cc7f780@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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.