From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30455 invoked by alias); 17 Sep 2002 23:56:01 -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 30445 invoked from network); 17 Sep 2002 23:56:00 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 17 Sep 2002 23:56:00 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D917A3CC6; Tue, 17 Sep 2002 19:55:57 -0400 (EDT) Message-ID: <3D87C10D.8030005@ges.redhat.com> Date: Tue, 17 Sep 2002 16:56:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron McCall Cc: GDB Mailing List Subject: Re: Register setting problem References: <20020917171141.A17795@sikorsky.com> <20020917211544.GA1746@nevyn.them.org> <20020917172248.A17838@sikorsky.com> <3D87A6A2.7020904@ges.redhat.com> <20020917185835.A25070@sikorsky.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00247.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. I think the snapshot (and hence the release :-() process is leaving a stray file behind. (I also recall someone mentioning this before :-( ). Look for config.cache, config.log, Makefile, or similar. The work around is to delete the dejagnu directory from the unpacked source tree. Andrew > 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 >