From: <rdiezmail-emacs@yahoo.de>
To: bug-gnu-emacs@gnu.org
Subject: configure script does not fail and stop when it should
Date: Thu, 25 Oct 2007 10:25:56 +0200 (CEST) [thread overview]
Message-ID: <105259.47841.qm@web25408.mail.ukl.yahoo.com> (raw)
Hi all:
I recently had some trouble building emacs 22.1 on Debian 4.0r1. I
don't know that much about emacs or Linux, but hopefully my experience
will help others avoid the following problems. I just downloaded the
sources and did:
./configure
make
Point 1) I have a fully-functional Linux system with X Windows, Gnome
and so on. When I build emacs, I expect it to automatically build with
X Windows support.
I would expect the configure script to detect a running/installed X
Windows, and then perhaps complain that the development headers /
libraries for X Windows are not available. I mean, I expect "configure"
to fail, that means, to NOT generate a makefile. It would be nice if it
then said something along the line "you probably need to install the X
Windows development files/package/whatever".
I know the INSTALL file says I should review the libraries that were
automatically found, but like the INSTALL file also says:
If the details printed by `configure' don't make any sense to
you, assume that `configure' did its job and proceed.
What I got instead was an Emacs binary that would not start due to some
weird TERMCAP error.
Point 2) After some googling, I finally realised I had to be explicit
and say:
./configure --with-x
But I did not have the development headers and so on. So I ended up
with the same lame emacs binary.
At this point I thought: if I explicitly say "I want X Windows", then
the "configure" script should fail and NOT generate a makefile if it
cannot find the necessary headers / libraries. Like I said above, it
would be nice if the "configure" script said in the error message
something along the line "you probably need to install the X Windows
development files/package/whatever".
I could probably read INSTALL thoroughly and learn a lot more in order
to avoid these problems, but I think these little things would help
save everybody's time.
Thanks,
Ruben
Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
http://de.yahoo.com/set
next reply other threads:[~2007-10-25 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 8:25 rdiezmail-emacs [this message]
2007-10-25 11:10 ` configure script does not fail and stop when it should Johan Bockgård
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=105259.47841.qm@web25408.mail.ukl.yahoo.com \
--to=rdiezmail-emacs@yahoo.de \
--cc=bug-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).