From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: CVS Head Compile Failure
Date: Mon, 02 Mar 2009 19:29:00 -0000 [thread overview]
Message-ID: <49AC339D.5070404@oarcorp.com> (raw)
In-Reply-To: <20090302191812.GB3632@adacore.com>
Joel Brobecker wrote:
>> -MP -MF .deps/rs6000-tdep.Tpo
>> /home/joel/test-gcc/gdb-cvs/src/gdb/rs6000-tdep.c
>> In file included from /home/joel/test-gcc/gdb-cvs/src/gdb/inferior.h:38,
>> from /home/joel/test-gcc/gdb-cvs/src/gdb/rs6000-tdep.c:24:
>> /home/joel/test-gcc/gdb-cvs/src/gdb/target.h:58:25: error:
>> gdb_signals.h: No such file or directory
>> make[2]: *** [rs6000-tdep.o] Error 1
>> make[2]: Leaving directory `/home/joel/test-gcc/b-gdb-powerpc/gdb'
>> make[1]: *** [all-gdb] Error 2
>> make[1]: Leaving directory `/home/joel/test-gcc/b-gdb-powerpc'
>>
>
> gdb_signals.h was moved to a subdirectory: gdb/common. A normal "cvs
> update" wouldn't checkout that directory. Can you make sure that this
> subdirectory is checked out and to a rebuild?
>
>
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.
--joel
RTEMS
--
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
next prev parent reply other threads:[~2009-03-02 19:29 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 [this message]
2009-03-02 19:33 ` Joel Brobecker
2009-03-02 19:50 ` Thiago Jung Bauermann
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=49AC339D.5070404@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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