From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: emacs 21.3 with X support?
Date: Sun, 13 Jun 2004 13:38:17 +0200 [thread overview]
Message-ID: <86brjny9g6.fsf@rumba.de.uu.net> (raw)
In-Reply-To: 0F3691CE-BCBC-11D8-9BF3-000A95C0C442@berkeley.edu
Aaron Steele <asteele@berkeley.edu> writes:
> is this output more useful?
Well, I can see that it looked but couldn't find it. But as I
already mentioned in another reply, you swapped the locations for the
libraries and for the include files.
If all of this doesn't help, you may have to install additional
packages. For example, there are often *-dev or *-devel packages
that contain the header files.
But your configure run indicates that it couldn't even find the X11
library libXt, and without that library, X11 pretty much won't run.
So that is an indicator that configure was looking in the wrong place.
Kai
prev parent reply other threads:[~2004-06-13 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 16:18 emacs 21.3 with X support? Aaron Steele
2004-06-12 17:20 ` Kai Grossjohann
2004-06-12 18:28 ` Eli Zaretskii
2004-06-12 17:47 ` Aaron Steele
2004-06-12 19:37 ` Kai Grossjohann
2004-06-12 22:01 ` Aaron Steele
2004-06-13 5:05 ` Eli Zaretskii
2004-06-13 11:38 ` Kai Grossjohann [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
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=86brjny9g6.fsf@rumba.de.uu.net \
--to=kai@emptydomain.de \
/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).