unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "James K. Lowden" <jklowden@speakeasy.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Ubuntu font of wisdom
Date: Sat, 17 Dec 2016 00:29:26 -0500	[thread overview]
Message-ID: <20161217002926.2fc5db735711a8d9e10744e5@speakeasy.net> (raw)
In-Reply-To: o31n1u$1i6$1@gioia.aioe.org

On Fri, 16 Dec 2016 21:41:18 +0000 (UTC)
Javier <nospam@nospam.invalid> wrote:

> > While I'm at it, the new version uses the ugly Motif-gray toolbar,
> > while the packaged version uses a much more attractive, colorful
> > toolbar (and puts the scrollabar on the right).  
> 
> It looks you are using different toolkits on 24 and 25 versions.
> Look at the output of M-x display-about-screen

Thank you.  Yes: 

GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll
bars)

> The available toolkits can be seen in the source code
> from ./configure --help:

Yes, I read INSTALL more carefully today, and surmised I want GTK+.  
Do you think if I successfully build with GTK+ that my fonts will
magically Just Work?  That would be nice.  

At the risk of going off-topic, I believe I've found the root of the
trouble, and it appears to be a bug in the configure script.  

When I practiced on a virtual machine (same Ubuntu, but
installed more recently) I got  a lovely GTK+ 25.1 build, with
no hiccups. Following the same instructions on my somewhat cruftier dev
box, I encountered problems: configure complained it can't find libpng.

Tedious inspection of the two configure.log files reveals the
difference: configure is attempting to use libpng16, despite it being
in an odd place.  

    gcc  -o  conftest \
    -g3 \
    -O2 \
    -pthread \
    -I/usr/include/librsvg-2.0 \
    -I/usr/include/gdk-pixbuf-2.0 \
    -I/usr/include/libpng12 \
    -I/usr/include/cairo \
    -I/usr/include/glib-2.0 \
    -I/usr/lib/x86_64-linux-gnu/glib-2.0/include \
    -I/usr/include/pixman-1 \
    -I/usr/include/freetype2 \
    -I/usr/include/libpng12 \
    -I/usr/local/anaconda/include/libpng16 \  <-- hello!  
    conftest.c \
    -lpng16 \
    -lz \
    -lm \
    -lX11 
    
Apparently, configure traverses /usr/local for include files but not
libraries.  Anaconda (the Python package manager)
uses /usr/loca/anaconda/{include,lib}.  configure's test fails because
libpng16 is not on the default library search path: 

	$ find /usr/local/ -name '*png16*so'
	/usr/local/anaconda/lib/libpng16.so

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.  

What I will do for the nonce is rename the directory
to /usr/local/..anaconda, or move it out of the way, and see if
configure can find its way.  

Other suggestions?  

--jkl


  reply	other threads:[~2016-12-17  5:29 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 [this message]
2016-12-17  6:02     ` Dan Espen
2016-12-17 17:04       ` James K. Lowden
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=20161217002926.2fc5db735711a8d9e10744e5@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).