Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: michael-ring@t-online.de (Michael Ring) To: matighet Cc: cygwin@sources.redhat.com Subject: Re: autoconf configure problems Date: Mon, 02 Oct 2000 18:21:50 +0200 Message-ID: References: <39D88FC4.8749FFD0@bbn.com> <4.3.1.2.20001002102152.01baf178@pop.ma.ultranet.com> <20001002114732.K13304@cygnus.com> <39D8B0D5.37945D79@bbn.com> In-Reply-To: <39D8B0D5.37945D79@bbn.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Sender: 320032306730-0001@t-dialin.net Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA29562 On Mon, 02 Oct 2000 11:59:17 -0400, you wrote: >uname -a yields > >CYGWIN_NT-4.0 GLOCKENSPIEL 1.1.2(0.21/3/2) 2000-06-06 22:20 i686 unknown > > >Do you suggest that I nuke my whole cygwin installation and put it back >from scratch? >How do I get rid of all the registry entries from old installations ? > >Thanks for the help >Michael > > Another shot would be to make the /g - Mount point a binary mountpoint. Sometimes configure scripts behave somewhat stange if they are started on a text-mounted filesystem. As your mounts for /usr/bin & /usr/lib are also missing I would recommend the following: put /g in binmode delete the source-package and do a 'tar zxvf PACKAGE.tar.gz' just to make sure that all files are binary now. try to configure .... if it does not work: update cygwin to latest release try with /g in binmode then revert /g to textmode & try again. Cheers, Michael Ah yes, sometimes configure-scripts leave config.log files in the directory where they were started in, have a look at the file, perhaps the information in config.log helps to solve the problem. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com