From: Ron McCall <rmccall@sikorsky.com>
To: GDB Mailing List <gdb@sources.redhat.com>
Subject: Re: Register setting problem
Date: Tue, 17 Sep 2002 15:59:00 -0000 [thread overview]
Message-ID: <20020917185835.A25070@sikorsky.com> (raw)
In-Reply-To: <3D87A6A2.7020904@ges.redhat.com>; from ac131313@ges.redhat.com on Tue, Sep 17, 2002 at 06:03:14PM -0400
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
next prev parent reply other threads:[~2002-09-17 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 14:12 Ron McCall
2002-09-17 14:15 ` Daniel Jacobowitz
2002-09-17 14:23 ` Ron McCall
2002-09-17 15:03 ` Andrew Cagney
2002-09-17 15:09 ` Ron McCall
2002-09-17 15:59 ` Ron McCall [this message]
2002-09-17 16:56 ` Andrew Cagney
2002-09-17 18:11 ` Ron McCall
2002-09-18 7:24 ` Ron McCall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020917185835.A25070@sikorsky.com \
--to=rmccall@sikorsky.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox