Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Nathanael Nerode <neroden@doctormoo.dyndns.org>
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: top level makefile.in
Date: Tue, 01 Oct 2002 19:40:00 -0000	[thread overview]
Message-ID: <3D9A5C93.7020900@redhat.com> (raw)
In-Reply-To: <20021001231948.GA17874@doctormoo.dyndns.org>

> On Tue, Oct 01, 2002 at 07:13:22PM -0400, Andrew Cagney wrote:
> 
>> 
> 
>> >Makefile.tpl, Makefile.def, and src-release should be included.  Eek.
> 
>> 
>> Ok.  Just adding them now...
>> 
> 
>> >You need to revert the change to 'configure' corresponding to my reverted
>> >change to Makefile.tpl/Makefile.in, until everyone's using src-release
>> >and my changes can be put back in full; the partial reversion is the
>> >cause of the build breakage.
> 
> I finished the reversion, so the build shouldn't be breaking.
> 
> 
>> 
>> Binutils are ok with this stuff (see other post).
>> 
>> Would you be able to commit the src-release file sometime in the next, 
>> er, 40 minutes?  That way GDB's snap will pick it up and start using it.
> 
> It's committed.
> 
> 
>> 
>> (Assuming that I get it added to GDB's modules file, also in the next 40 
>> minutes :-)
> 
> Over to you. :-)

Well the snap is using src-release:

==> Making gdb+dejagnu-20021002/
./configure: -e: command not found
Created "Makefile" in 
/sourceware/snapshot-tmp/gdb-snapshot/current-gdb+dejagnu/
make-snapshot/src
Configuring intl...
creating cache ../config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for ranlib... ranlib
checking for POSIXized ISC... no
checking for ANSI C header files... yes
checking for working const... yes
checking for inline... inline
checking for off_t... yes

but then eventually barfs:

checking for working makeinfo... found
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking how to run the C preprocessor... (cached) gcc -E
checking for stdlib.h... (cached) yes
checking for strcmp... yes
checking whether to enable maintainer-specific portions of Makefiles... no
updating cache ../../../config.cache
creating ./config.status
creating Makefile
creating calc.h
Configuring utils...
loading cache ../config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking host system type... sparc-sun-sunos4.1.1
checking target system type... sparc-sun-sunos4.1.1
checking build system type... sparc-sun-sunos4.1.1
creating ./config.status
creating Makefile
make[3]: *** No rule to make target `configure-target'.  Stop.
make[2]: *** [do-proto-toplev] Error 2
make[1]: *** [gdb-tar] Error 2
make: *** [gdb+dejagnu.tar] Error 2

I think this needs a tweak:

         ./configure sun4
         $(MAKE) configure-target \
             ALL_GCC="" ALL_GCC_C="" ALL_GCC_CXX="" \
             CC_FOR_TARGET="$(CC)" CXX_FOR_TARGET="$(CXX)"
         # Make links, and run "make diststuff" or "make info" when needed.
         rm -rf proto-toplev ; mkdir proto-toplev
         set -e ; dirs="$(TOOL) $(DEVO_SUPPORT) $(SUPPORT_FILES)" ; \

It looks like the configure-target rule was lost from Makefile.in/Makefile?

Anyway, I think the other Makefile.in changes can be pushed out (so 
people stop reporting broken `make install') and then I guess this is next.

Andrew



      reply	other threads:[~2002-10-02  2:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021001104833.E25369@bubble.sa.bigpond.net.au>
     [not found] ` <20021001012213.GA16275@nevyn.them.org>
     [not found]   ` <20021001114136.F25369@bubble.sa.bigpond.net.au>
     [not found]     ` <3D991AAC.4010207@redhat.com>
     [not found]       ` <20021001163755.M25369@bubble.sa.bigpond.net.au>
2002-10-01  8:36         ` Andrew Cagney
2002-10-01  8:51     ` Andrew Cagney
2002-10-01 15:50       ` Nathanael Nerode
2002-10-01 16:13         ` Andrew Cagney
2002-10-01 16:24           ` Nathanael Nerode
2002-10-01 19:40             ` Andrew Cagney [this message]

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=3D9A5C93.7020900@redhat.com \
    --to=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=neroden@doctormoo.dyndns.org \
    /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