From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, DJ Delorie <dj@delorie.com>,
neroden@twcny.rr.com
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: (toplevel patch) Configure in Makefile, version 3.
Date: Thu, 05 Dec 2002 12:48:00 -0000 [thread overview]
Message-ID: <3DEFBB9E.8090003@redhat.com> (raw)
In-Reply-To: <20021205203416.GA17942@nevyn.them.org>
> On Thu, Dec 05, 2002 at 03:30:29PM -0500, Andrew Cagney wrote:
>
>> DJ, humor me.
>>
>>
>
>> >He he he. Did you try typing "make" ?
>> >
>> >Hopefully you'll be pleasantly surprised...
>
>>
>>
>> So how does a GDB snapshot work again? The documentation states:
>>
>> $ gmake -f Makefile.in gdb.tar
>> Makefile.in:7776: *** missing separator. Stop.
>
>
> Weren't you using src-release for this now?
>
> However, src-release will need updating to actually run the configure
> targets.
I'm doing what ever the doco tells me :-)
http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC151
(hmm, the doco's out-of-date for the mainline - my bad, sorry :-()
back to the new problem:
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
gmake configure-target \
ALL_GCC="" ALL_GCC_C="" ALL_GCC_CXX="" \
CC_FOR_TARGET="cc" CXX_FOR_TARGET="g++"
gmake[3]: Entering directory `/notnfs/cagney/GDB/src'
Makefile:6618: warning: overriding commands for target
`sun4/libiberty/Makefile'
Makefile:1258: warning: ignoring old commands for target
`sun4/libiberty/Makefil
e'
gmake[3]: *** No rule to make target `cc', needed by
`sun4/libstdc++-v3/multilib
.out'. Stop.
gmake[3]: Leaving directory `/notnfs/cagney/GDB/src'
gmake[2]: *** [do-proto-toplev] Error 2
gmake[2]: Leaving directory `/notnfs/cagney/GDB/src'
gmake[1]: *** [gdb-tar] Error 2
gmake[1]: Leaving directory `/notnfs/cagney/GDB/src'
gmake: *** [gdb.tar] Error 2
cagney@torrens$
It's pretty easy to reproduce.
gmake -f src-release gdb.tar
Andrew
next prev parent reply other threads:[~2002-12-05 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 18:27 Nathanael Nerode
2002-12-05 12:10 ` Andrew Cagney
2002-12-05 12:15 ` DJ Delorie
2002-12-05 12:20 ` Andrew Cagney
2002-12-05 12:22 ` DJ Delorie
2002-12-05 12:30 ` Andrew Cagney
2002-12-05 12:36 ` Daniel Jacobowitz
2002-12-05 12:48 ` Andrew Cagney [this message]
2002-12-05 12:51 ` DJ Delorie
2002-12-05 15:15 ` Andrew Cagney
2002-12-05 16:54 Nathanael Nerode
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=3DEFBB9E.8090003@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@delorie.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.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