From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Joel Sherrill <joel.sherrill@oarcorp.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: CVS Head Compile Failure
Date: Mon, 02 Mar 2009 19:50:00 -0000 [thread overview]
Message-ID: <1236023410.8949.79.camel@localhost.localdomain> (raw)
In-Reply-To: <20090302193347.GC3632@adacore.com>
El lun, 02-03-2009 a las 11:33 -0800, Joel Brobecker escribió:
> > Thanks. I have been avoiding "cvs up -Pd" since it pulls
> > in the rest of the one build tree but apparently it was
> > needed this time.
> >
> > It builds now.
>
> Excellent. I avoid the "-d" switch too, for the very same reason.
> I don't know if you did a "cvs up -d common" or a plain "cvs up -d",
> but you might have pulled more than necessary (in particular in
> the testsuite directory, such as testsuite/gdb.tk), and that might
> cause you some trouble later. When I need to pull one directory,
> I specify exactly which one I want.
Just FYI: I don't use cvs update at all. I have a "src -> ." link in the
src dir, and from there I do a "cvs -d $(cat CVS/Root) co gdb". Tends to
work well, except for this weird half-patch issue I posted a message
about.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-03-02 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 18:52 Joel Sherrill
2009-03-02 19:18 ` Joel Brobecker
2009-03-02 19:29 ` Joel Sherrill
2009-03-02 19:33 ` Joel Brobecker
2009-03-02 19:50 ` Thiago Jung Bauermann [this message]
2009-03-03 16:34 ` Doug Evans
2009-03-03 16:38 ` Joel Sherrill
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=1236023410.8949.79.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.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