From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.bugs Subject: configure script does not fail and stop when it should Date: Thu, 25 Oct 2007 10:25:56 +0200 (CEST) Message-ID: <105259.47841.qm@web25408.mail.ukl.yahoo.com> Reply-To: rdiezmail-emacs@yahoo.de NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1193302961 26691 80.91.229.12 (25 Oct 2007 09:02:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Oct 2007 09:02:41 +0000 (UTC) To: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Oct 25 11:02:42 2007 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Ikybx-0005Bh-09 for geb-bug-gnu-emacs@m.gmane.org; Thu, 25 Oct 2007 11:02:41 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ikybo-0001y8-Mb for geb-bug-gnu-emacs@m.gmane.org; Thu, 25 Oct 2007 05:02:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iky2R-0006qu-4m for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 04:25:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iky2P-0006qi-Gz for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 04:25:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iky2P-0006qf-FI for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 04:25:57 -0400 Original-Received: from web25408.mail.ukl.yahoo.com ([217.12.10.142]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Iky2P-0001jn-7P for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 04:25:57 -0400 Original-Received: (qmail 48533 invoked by uid 60001); 25 Oct 2007 08:25:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=W2cHrOG1EPoWujzQ9y5JbHgvUufWm+te6r8QyiNZmZ5eMVjauAqAbKqwwzU6u9LH+9oIXWXSqpu+bFeK5jbx9YZYZmfLCSV4/2PVjvze6+VNwRIXU1avbyfPQwh4Zq0zOPMdzFWx55aJouQE5B43AtbHbQb5gyOB9+LmEks+52Y=; X-YMail-OSG: w0MrZogVM1n2ICodKl0NdUnFClK2psd6Qrd20NSQhpz1B2ksiG9bdSH73yoUHF0iEg-- Original-Received: from [82.207.169.34] by web25408.mail.ukl.yahoo.com via HTTP; Thu, 25 Oct 2007 10:25:56 CEST X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) X-Mailman-Approved-At: Thu, 25 Oct 2007 05:01:26 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:16830 Archived-At: 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