From: "James K. Lowden" <jklowden@speakeasy.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Ubuntu font of wisdom
Date: Sat, 17 Dec 2016 12:04:25 -0500 [thread overview]
Message-ID: <20161217120425.29862805b94ff5d4257b5f34@speakeasy.net> (raw)
In-Reply-To: o32kbe$irc$2@dont-email.me
On Sat, 17 Dec 2016 01:02:42 -0500
Dan Espen <despen@verizon.net> wrote:
> > I don't see any way to exclude a directory from configure's search
> > path. I'm grateful for the many years between today and the last
> > time I was responsible for a configure.ac. I can report configure
> > is broken: it should either not use anaconda's tree, or it should
> > use both forks.
...
> > Other suggestions?
>
> On Fedora, I get libpng16 out of /usr/include and /usr/lib64.
> I think you need to install a devel package like
> libpng-devel.
That was my first tack. At this stage of the game on Ubuntu LTS, GTK+
relies on png 12. You can have GTK3+ or png 16, but not both.
Your suggestion may illuminate part of the root of the problem,
though. Most packagers undoubtedly are running relatively new systems,
and have png 16 installed as a matter of course. And most Anaconda
usrs don't situate the package in /usr/local.
If I put my anaconda elsewhere or ran closer to the leading edge
(either one) my anaconda installation wouldn't have come into play,
because configure would have found /usr/local/lib/libpng16.so. It's
only the combination that manifests the defect.
--jkl
next prev parent reply other threads:[~2016-12-17 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 22:43 Ubuntu font of wisdom James K. Lowden
2016-12-16 21:41 ` Javier
2016-12-17 5:29 ` James K. Lowden
2016-12-17 6:02 ` Dan Espen
2016-12-17 17:04 ` James K. Lowden [this message]
2016-12-17 17:53 ` Dan Espen
2016-12-17 18:59 ` James K. Lowden
2016-12-18 21:32 ` Tomas Nordin
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=20161217120425.29862805b94ff5d4257b5f34@speakeasy.net \
--to=jklowden@speakeasy.net \
--cc=help-gnu-emacs@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.
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).