From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 513 invoked by alias); 19 Feb 2003 13:39:26 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 506 invoked from network); 19 Feb 2003 13:39:26 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 19 Feb 2003 13:39:26 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 056922D37; Wed, 19 Feb 2003 08:44:12 -0500 (EST) Message-ID: <3E538A2A.6070407@redhat.com> Date: Wed, 19 Feb 2003 13:39:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeroen Ruigrok/asmodai Cc: gdb@sources.redhat.com Subject: Re: host guess damaged in CVS? References: <20030218173931.GW25165@nexus.ninth-circle.org> <3E529453.3080704@redhat.com> <20030218204354.GC50444@nexus.ninth-circle.org> <3E52AA3E.8050409@redhat.com> <20030219091444.GJ50444@nexus.ninth-circle.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00341.txt.bz2 > -On [20030218 22:45], Andrew Cagney (ac131313@redhat.com) wrote: > >>You can do: >> >>$ sh GDB/src/config.guess >>i686-pc-linux-gnu > > > Funny: > > bentss@benremedy04 (/usr/users/bentss/asmodai/src-test) # ls -asl config* > 41 -rwxr-xr-x 1 bentss bentss 41025 Feb 19 09:42 config.guess > 136 -rwxr-xr-x 1 bentss bentss 136859 Feb 19 09:42 configure > > bentss@benremedy04 (/usr/users/bentss/asmodai/src-test) # ./configure --prefix=/usr/users/bentss/asmodai --disable-nls > loading cache ./config.cache > checking host system type... configure: error: can not guess host type; you must specify one > > bentss@benremedy04 (/usr/users/bentss/asmodai/src-test) # ./config.guess > alphaev67-dec-osf5.1 Well, there goes that theory :-( > autoconf issue perhaps then? Yes, or SH bug. Using current sources, can you isolate this down to a single subdirectory and then use `sh -x' on it? Hmm, can you also try configuring in a separate directory vis: cd /tmp /path/to/configure .... it might be that. Andrew