Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: gdb-patches@sources.redhat.com
Subject: [commit/sim] Force generation of configure and other stuff; Was: [commit/sim] switch autoconf 2.59
Date: Wed, 12 Jan 2005 16:29:00 -0000	[thread overview]
Message-ID: <41E5501A.3000907@gnu.org> (raw)
In-Reply-To: <Pine.BSF.4.58.0501112040210.64105@dair.pair.com>

Hans-Peter Nilsson wrote:
> 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:

I've still a few ideas.

> ... (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.

That config failure reeks of the problem I fixed.  Seems that you need 
to really want to run the new autoconf (unlike the old) - even though I 
ran autoconf in all those directories it didn't do as I ask.  I've 
re-run it with --force and that's had an effect.

The next problem is somewhere in sim/, try running make all-sim; make 
all-sim.  The first run barfs with no Makefile created, while the second 
prints a fail but makefile still manages to exit with zero status.  A 
guess is that GDB then managed to stumble along and build.

This also rewrites SIM_AC_OUTPUT to be 2.59 ``compliant'' (well at least 
it now generates makefiles); and zaps any other stray AC_AUX_DIRECTORY 
macros.

With that committed, I'm seeing another autoconf bug.  It's using 
ac_objext before it's been defined and that is leading to autoconf test 
failures (it looks for "conftest." instead of "conftest.o").

:-/

Andrew


  reply	other threads:[~2005-01-12 16:29 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
2005-01-12 16:29           ` Andrew Cagney [this message]
2005-01-12 17:15             ` [commit/sim] Add common/common.m4; Was: " 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=41E5501A.3000907@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hp@bitrange.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