This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CVS Head Compile Failure


Doug Evans wrote:
On Mon, Mar 2, 2009 at 11:33 AM, Joel Brobecker <brobecker@adacore.com> wrote:
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.

One useful idiom of cvs is not use "cvs update" to update. Instead just re-checkout the module.

cvs up -Pd is annoying in the top level directory (src), yes.
In subdirectories it _should_ be just fine, and in pretty much every
subdirectory it is (opcodes, bfd, include, etc.).

Alas in gdb it isn't necessarily what you want because it brings in gdbtk.
Thanks for the information.  This is for the
script that updates and tests the RTEMS tools
targets so they need to run reliably.

I will be changing the way they update the tree.

--joel

--
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
  Support Available             (256) 722-9985



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]