unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: a.daniel.eliason@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Emacs 26.1: ./configure does not find my GTK
Date: Fri, 16 Nov 2018 07:29:37 -0800 (PST)	[thread overview]
Message-ID: <0cda1bb2-c3c4-40ab-932b-8ce7fb8b594e@googlegroups.com> (raw)

I'm trying to compile from the current 26.1 tarball on CentOS..  It stops because it can't find by GTK. Anybody have similar problem?

My GTK libs are in to /usr/lib64:

  -bash-4.2$ ls /usr/lib64/libgtk*
  /usr/lib64/libgtk-3.so.0  /usr/lib64/libgtk-3.so.0.2200.26  /usr/lib64/libgtk-x11-2.0.so.0  /usr/lib64/libgtk-x11-2.0.so.0.2400.31

There is no GTK in my 32 bit libs, however:

  -bash-4.2$ ls /usr/lib/libgtk*
  ls: cannot access /usr/lib/libgtk*: No such file or directory
  -bash-4.2$ 

When I run./configure, it does not find the 64 bit libs, apparently:

  <...clipped>
  checking for GTK... no
  checking for GTK... no
  checking for DBUS... yes
  checking for dbus_watch_get_unix_fd... yes
  checking for dbus_type_is_valid... yes
  checking for dbus_validate_bus_name... yes
  checking for dbus_validate_path... yes
  checking for dbus_validate_interface... yes
  checking for dbus_validate_member... yes
  checking for GSETTINGS... yes
  checking whether GSettings is in gio... yes
  checking for GOBJECT... yes
  checking for lgetfilecon in -lselinux... yes
  checking for LIBGNUTLS... no
  checking for LIBSYSTEMD... no
  checking sys/inotify.h usability... yes
  checking sys/inotify.h presence... yes
  checking for sys/inotify.h... yes
  checking for inotify_init1... yes
  checking for xaw3d... no
  checking for libXaw... configure: error: No X toolkit could be found.
  If you are sure you want Emacs compiled without an X toolkit, pass
    --with-x-toolkit=no
  to configure.  Otherwise, install the development libraries for the toolkit
  that you want to use (e.g. Gtk+) and re-run configure.
  -bash-4.2$

I did try "yum install gtk+", and it did a bunch of work, but it made no difference.  I even tried installing "xaw" from yum, 'cause I saw ./configure was looking for it, but that made no difference either.

I tried setting LD_LIBRARY_PATH, but it did not help

  -bash-4.2$ echo $LD_LIBRARY_PATH
  /usr/lib64:/usr/lib:/usr/local/lib64:/usr/local/lib
  -bash-4.2$

My /etc/ld.so.conf is

  -bash-4.2$ cat /etc/ld.so.conf
  include ld.so.conf.d/*.conf
  /usr/lib64
  /usr/lib
  -bash-4.2$ cat /etc/ld.so.conf.d/*.conf
  /usr/local/lib
  /usr/local/lib64
  /usr/local/lib
  /usr/local/lib64
  /usr/local/lib
  /usr/local/lib64
  /usr/lib64/mysql
  /usr/pgsql-9.4/lib
  -bash-4.2$

It seems like emacs ./configure really doesn't know how to deal with the 64 bit libraries?? 


             reply	other threads:[~2018-11-16 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 15:29 a.daniel.eliason [this message]
2018-11-16 17:34 ` Emacs 26.1: ./configure does not find my GTK Glenn Morris
2018-11-16 18:29 ` Javier
2018-11-19  7:28   ` a.daniel.eliason
     [not found] ` <mailman.4148.1542389693.1284.help-gnu-emacs@gnu.org>
2018-11-19  7:26   ` a.daniel.eliason

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=0cda1bb2-c3c4-40ab-932b-8ce7fb8b594e@googlegroups.com \
    --to=a.daniel.eliason@gmail.com \
    --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).