From: Lars Ingebrigtsen <larsi@gnus.org>
To: 19831@debbugs.gnu.org
Subject: bug#19831: 25.0.50; Can't build emacs 25.0.5 with libpng16 support (only libpng15)
Date: Sat, 26 Dec 2015 19:10:11 +0100 [thread overview]
Message-ID: <87h9j5jd30.fsf@gnus.org> (raw)
In-Reply-To: <87zj8kd21h.fsf@violet.siamics.net> (Ivan Shmakov's message of "Wed, 11 Feb 2015 13:13:14 +0000")
Ivan Shmakov <ivan@siamics.net> writes:
>>>>>> Tory S Anderson <torys.anderson@gmail.com> writes:
>
> […]
>
> > And yet, to my frustration, afterwards I STILL received:
>
> > $ libpng-config --cflags -I/home/torys/anaconda/include/libpng15
>
> > I can't seem to get around this. Any suggestions would be
> > appreciated.
>
> My guess is that the ‘libpng-config’ executable coming first in
> your $PATH is still the one belonging to libpng15, not libpng16.
>
> What’s the output of $ type libpng-config? Do that file’s mtime
> and ctime (try $ stat on the file) reflect the date and time the
> new version was installed?
>
> If it’s indeed the “wrong” libpng-config which gets used, –
> check the value of the $PATH environment variable itself and
> either adjust as needed for the directory with the “right”
> libpng-config to come first there, /or/ somehow prevent the
> “wrong” file from being found (either $ chmod a-x it, or perhaps
> rename it.)
More information was requested, but no response was given within a few
months, so I'm closing this bug report. If the problem still exists,
please reopen this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2015-12-26 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 17:57 bug#19831: 25.0.50; Can't build emacs 25.0.5 with libpng16 support (only libpng15) Tory S. Anderson
2015-02-10 19:51 ` Eli Zaretskii
2015-02-10 22:40 ` Tory S. Anderson
2015-02-11 13:13 ` Ivan Shmakov
2015-12-26 18:10 ` Lars Ingebrigtsen [this message]
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=87h9j5jd30.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19831@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 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.