From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11509 invoked by alias); 17 Sep 2002 22:59:09 -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 11498 invoked from network); 17 Sep 2002 22:59:08 -0000 Received: from unknown (HELO mail3.utc.com) (192.249.46.81) by sources.redhat.com with SMTP; 17 Sep 2002 22:59:08 -0000 Received: (from uucp@localhost) by mail3.utc.com (8.10.0/8.10.0) id g8HMx6806814 for ; Tue, 17 Sep 2002 18:59:06 -0400 (EDT) Received: from uusnwa0n.utc.com(159.82.82.46) by mail3.utc.com via csmap (V6.0) id srcAAAw_aytn; Tue, 17 Sep 02 18:59:06 -0400 Received: from ronbo.sikorsky.com (ronbo.sikorsky.com [140.76.12.150]) by uusnwa0n.utc.com (Switch-2.2.4/Switch-2.2.4) with ESMTP id g8HMx4W25268 for ; Tue, 17 Sep 2002 18:59:04 -0400 (EDT) Received: (from s29299@localhost) by ronbo.sikorsky.com (8.11.6+Sun/8.11.6) id g8HMwZ027281 for gdb@sources.redhat.com; Tue, 17 Sep 2002 18:58:35 -0400 (EDT) X-Authentication-Warning: ronbo.sikorsky.com: s29299 set sender to rmccall@sikorsky.com using -f Date: Tue, 17 Sep 2002 15:59:00 -0000 From: Ron McCall To: GDB Mailing List Subject: Re: Register setting problem Message-ID: <20020917185835.A25070@sikorsky.com> Mail-Followup-To: GDB Mailing List References: <20020917171141.A17795@sikorsky.com> <20020917211544.GA1746@nevyn.them.org> <20020917172248.A17838@sikorsky.com> <3D87A6A2.7020904@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3D87A6A2.7020904@ges.redhat.com>; from ac131313@ges.redhat.com on Tue, Sep 17, 2002 at 06:03:14PM -0400 X-SW-Source: 2002-09/txt/msg00246.txt.bz2 On Tue, Sep 17, 2002 at 06:03:14PM -0400, Andrew Cagney wrote: > Suggest grabbing a snapshot from the latest (5.3) branch: > ftp://sources.redhat.com/pub/gdb/snapshots/branch/. That way we know > it is fixed in the next GDB release. OK, I grabbed gdb+dejagnu.tar.bz2 which appears to be symlinked to gdb+dejagnu-5.2.90_20020917.tar.bz2. I am getting a configure error: checking whether make sets ${MAKE}... (cached) yes configure: error: source directory already configured; run make distclean there first configure: error: .../../../../gdb+dejagnu-5.2.90_20020917/dejagnu/example/calc/configure failed for example/calc Configure in /export/home0/software/build/build-gdb/dejagnu failed, exiting. The config.log file in the calc subdirectory looks clean (though there is a confdefs.h file left over containing only a single newline character): This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:562: checking for a BSD compatible install configure:615: checking whether build environment is sane configure:672: checking whether make sets ${MAKE} I then tried the suggested action of running make distclean in the GDB source directory but that results in: make: *** No rule to make target `distclean'. Stop. I get the same error in the dejagnu subdirectory but I get a different error in the dejagnu/example subdirectory: Makefile:317: warning: overriding commands for target `check-recursive' Makefile:111: warning: ignoring old commands for target `check-recursive' make: *** No rule to make target `../config.status', needed by `Makefile'. Stop. In the dejagnu/example/calc subdirectory, I get the same error minus the two warnings. Does anyone know how to get around this problem? Should I try yesterday's snapshot instead? I am building GDB in a separate directory outside of the source tree as I usually do and the source tree is clean from the tarball. Thanks for the help! Ron McCall