From: Karel Gardas <kgardas@objectsecurity.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb head fails to compile for arm-elf target.
Date: Mon, 16 Feb 2004 20:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.43.0402162151410.19250-100000@thinkpad.wg-ro-gar1.inext.cz> (raw)
In-Reply-To: <20040216204239.GA15919@nevyn.them.org>
On Mon, 16 Feb 2004, Daniel Jacobowitz wrote:
> > Err, I had an impression that if checkout worked correctly with modules
> > and all depending modules, then update will also work this way. :-(
> > (especially when I read it on the gcc page: ``Update the src tree with the
> > same sequence of commands that you used to check out that tree initially,
> > invoked from the src directory (NOT from within the combined tree).'')
>
> Ah, but that's not what you did. Here's the problem: cvs checkout
> takes module names and cvs update takes directory names.
>
> If you used "cvs -d 'whatever' co binutils newlib gdb dejagnu" from the
> directory containing src/, everything would be updated.
Indeed! I've just found my mistake after sending this email. Please excuse
me for all this noise on gdb mailing list.
Anyway, thanks for your kind help,
Karel
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
prev parent reply other threads:[~2004-02-16 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 18:27 Karel Gardas
2004-02-16 18:34 ` Daniel Jacobowitz
2004-02-16 18:39 ` Karel Gardas
2004-02-16 18:42 ` Daniel Jacobowitz
2004-02-16 18:46 ` Karel Gardas
2004-02-16 18:50 ` Daniel Jacobowitz
2004-02-16 19:54 ` Karel Gardas
2004-02-16 20:42 ` Daniel Jacobowitz
2004-02-16 20:53 ` Karel Gardas [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=Pine.LNX.4.43.0402162151410.19250-100000@thinkpad.wg-ro-gar1.inext.cz \
--to=kgardas@objectsecurity.com \
--cc=drow@false.org \
--cc=gdb@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