CVS Head Compile Failure

CVS Head Compile Failure

[Joel Sherrill]

Hi,

I don't know if this is a partial commit or
something else.  I am targeting powerpc-rtems
(e.g. powerpc-elf with psim enabled.

gcc -g -O2   -I. -I/home/joel/test-gcc/gdb-cvs/src/gdb 
-I/home/joel/test-gcc/gdb-cvs/src/gdb/common 
-I/home/joel/test-gcc/gdb-cvs/src/gdb/config 
-DLOCALEDIR="\"/home/joel/test-gcc/install/share/locale\"" 
-DHAVE_CONFIG_H -I/home/joel/test-gcc/gdb-cvs/src/gdb/../include/opcode 
-I/home/joel/test-gcc/gdb-cvs/src/gdb/../readline/.. -I../bfd 
-I/home/joel/test-gcc/gdb-cvs/src/gdb/../bfd 
-I/home/joel/test-gcc/gdb-cvs/src/gdb/../include -I../libdecnumber 
-I/home/joel/test-gcc/gdb-cvs/src/gdb/../libdecnumber  
-I/home/joel/test-gcc/gdb-cvs/src/gdb/gnulib -Ignulib  -DMI_OUT=1 
-DTUI=1   -Wall -Wdeclaration-after-statement -Wpointer-arith 
-Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch 
-Wno-char-subscripts -Werror -c -o rs6000-tdep.o -MT rs6000-tdep.o -MMD 
-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'

-- 
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

Re: CVS Head Compile Failure

[Joel Brobecker]

> -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?

-- 
Joel

Re: CVS Head Compile Failure

[Joel Sherrill]

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

Re: CVS Head Compile Failure

[Joel Brobecker]

> 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.

-- 
Joel

Re: CVS Head Compile Failure

[Thiago Jung Bauermann]

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

Re: CVS Head Compile Failure

[Doug Evans]

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.

Re: CVS Head Compile Failure

[Joel Sherrill]

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