From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Ian Lance Taylor <ian@wasabisystems.com>,
Andrew Cagney <cagney@gnu.org>, Manoj Iyer <manjo@austin.ibm.com>,
gdb@sources.redhat.com
Subject: Re: tcl cannot build 64bit.
Date: Wed, 10 Mar 2004 16:05:00 -0000 [thread overview]
Message-ID: <20040310160535.GA489@nevyn.them.org> (raw)
In-Reply-To: <jeeks0itbl.fsf@sykes.suse.de>
On Wed, Mar 10, 2004 at 05:02:22PM +0100, Andreas Schwab wrote:
> Ian Lance Taylor <ian@wasabisystems.com> writes:
>
> > The src directory is used for a number of different packages, not just
> > gdb.
>
> Yes, I know.
>
> > If you 'cvs co gdb' and then avoid using 'cvs update -d' at top level,
> > you should be OK.
>
> Not using -d is not an option. And the gdbtk directory even exists on the
> branch.
If you don't want to end up building Insight, update by using "checkout
gdb". Unfortunately, --disable-gdbtk doesn't fix the top level from
deciding gdb depends on tcl; that could be fixed in configure...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-10 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 21:10 Manoj Iyer
2004-03-09 21:20 ` Andrew Cagney
2004-03-09 21:34 ` Manoj Iyer
2004-03-09 22:03 ` Andreas Schwab
2004-03-09 22:05 ` Andreas Schwab
2004-03-09 22:27 ` Andrew Cagney
2004-03-09 22:55 ` Andreas Schwab
2004-03-10 1:34 ` Andrew Cagney
2004-03-10 5:46 ` Manoj Iyer
2004-03-10 9:13 ` Andreas Schwab
2004-03-10 9:12 ` Andreas Schwab
2004-03-10 15:25 ` Ian Lance Taylor
2004-03-10 16:02 ` Andreas Schwab
2004-03-10 16:05 ` Daniel Jacobowitz [this message]
2004-03-10 16:11 ` Manoj Iyer
2004-03-10 17:22 ` Andreas Schwab
2004-03-10 17:30 ` Ian Lance Taylor
2004-03-12 22:26 ` Manoj Iyer
2004-03-16 23:50 ` Andrew Cagney
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=20040310160535.GA489@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.com \
--cc=manjo@austin.ibm.com \
--cc=schwab@suse.de \
/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