From: Daniel Jacobowitz <drow@false.org>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb head fails to compile for arm-elf target.
Date: Mon, 16 Feb 2004 20:42:00 -0000 [thread overview]
Message-ID: <20040216204239.GA15919@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0402162052020.19250-100000@thinkpad.wg-ro-gar1.inext.cz>
On Mon, Feb 16, 2004 at 08:54:10PM +0100, Karel Gardas wrote:
> On Mon, 16 Feb 2004, Daniel Jacobowitz wrote:
>
> > > Do you think it's worth the test to freshly checkout whole tree again?
> > > Before build I have just rm -rf combined and updated gcc and src
> > > directories, src by: cvs -q up -Pd binutils newlib gdb dejagnu -- do you
> > > think that's the reason for failure?
> > >
> > > Thanks,
> >
> > Absolutely. You can't update just a few directories and relibly expect
> > things to work. At a minimum, you would also need: opcodes bfd gas ld
> > include libiberty.
>
> 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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-16 20:42 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 [this message]
2004-02-16 20:53 ` Karel Gardas
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=20040216204239.GA15919@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kgardas@objectsecurity.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