From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/sim] switch autoconf 2.59
Date: Wed, 12 Jan 2005 02:00:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0501112040210.64105@dair.pair.com> (raw)
In-Reply-To: <41E47C74.3050607@gnu.org>
On Tue, 11 Jan 2005, Andrew Cagney wrote:
> Hans-Peter Nilsson wrote:
> > On Tue, 11 Jan 2005, Andrew Cagney wrote:
> >>Before commiting this I did a full cross build (using gdb_mbuild.sh).
> > Looks like that only builds gdb.
>
> Why do you say that (yes I can read the subject)? It builds the GDB the
> source tree (which includes the sim) and typically GDB won't link if the
> sim build fails?
Ah, well, then I'm fresh out of wild guesses why it wasn't
noticed that the frv sim (and presumably all CGEN targets and
SIM_AC_OUTPUT users) fails building. To make sure nothing had
crept in locally, I just rechecked; checked out a brand new
"gdb" and did "$srcdir/configure --target=frv-elf && make all"
elsewhere. Host is i686-pc-linux-gnu (FC2), but I see this on
Debian Woody too:
... (from $build/sim)
configure: configuring in frv
configure: running /bin/sh '/home/hp/newgdb/src/sim/frv/configure' --prefix=/usr/local
'--cache-file=./config.cache' '--build=i686-pc-linux-gnu' '--host=i686-pc-linux-gnu' '--target=frv-elf' '--program-transform-name=s,^,frv-elf-,; ' '--srcdir=/home/hp/newgdb/src/sim' 'CC=gcc' 'CFLAGS=-g -O2' 'LDFLAGS=' 'build_alias=i686-pc-linux-gnu' 'host_alias=i686-pc-linux-gnu' 'target_alias=frv-elf' --cache-file=.././config.cache --srcdir=/home/hp/newgdb/src/sim/frv
configure: loading cache .././config.cache
configure: error: cannot run
configure: error: /bin/sh
'/home/hp/newgdb/src/sim/frv/configure' failed for frv
Re-doing the configure and make step, changing the "all" to
"all-gdb" (as in gdb_mbuild.sh), causes the same failure.
brgds, H-P
next prev parent reply other threads:[~2005-01-12 2:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 3:40 Andrew Cagney
2005-01-08 4:07 ` Daniel Jacobowitz
2005-01-10 16:18 ` Andrew Cagney
2005-01-11 20:20 ` Hans-Peter Nilsson
2005-01-11 21:06 ` Andrew Cagney
2005-01-12 1:17 ` Hans-Peter Nilsson
2005-01-12 1:26 ` Andrew Cagney
2005-01-12 2:00 ` Hans-Peter Nilsson [this message]
2005-01-12 16:29 ` [commit/sim] Force generation of configure and other stuff; Was: " Andrew Cagney
2005-01-12 17:15 ` [commit/sim] Add common/common.m4; " Andrew Cagney
2005-01-13 4:04 ` Hans-Peter Nilsson
2005-01-13 13:17 ` Hans-Peter Nilsson
2005-01-13 21:50 ` Andrew Cagney
2005-01-14 20:11 ` [commit/sim] flip and separate; Was: " Andrew Cagney
2005-01-14 21:46 ` Hans-Peter Nilsson
2005-01-12 17:53 ` [commit/sim] Force generation of configure and other stuff; " Hans-Peter Nilsson
2005-01-12 18:12 ` Andrew Cagney
2005-01-12 18:19 ` Hans-Peter Nilsson
2005-01-12 18:50 ` Andrew Cagney
2005-01-13 2:01 ` Hans-Peter Nilsson
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=Pine.BSF.4.58.0501112040210.64105@dair.pair.com \
--to=hp@bitrange.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@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