Re: [commit] note non-building architectures

[Andrew Cagney <cagney@gnu.org>]

Hans-Peter Nilsson wrote:

Just FYI, I currently see:

  -I/home/cagney/PENDING/Werror/src/sim/cris -I../common 
-I/home/cagney/PENDING/Werror/src/sim/cris/../common -I../../include 
-I/home/cagney/PENDING/Werror/src/sim/cris/../../include -I../../bfd 
-I/home/cagney/PENDING/Werror/src/sim/cris/../../bfd -I../../opcodes 
-I/home/cagney/PENDING/Werror/src/sim/cris/../../opcodes -I../../intl 
-I/home/cagney/PENDING/Werror/src/sim/cris/../../intl -g -O 
/home/cagney/PENDING/Werror/src/sim/cris/arch.c
/bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../common/genmloop.sh \
         -mono -no-fast -pbb -switch semcrisv10f-switch.c \
         -cpu crisv10f -infile 
/home/cagney/PENDING/Werror/src/sim/cris/mloop.in
/bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../common/genmloop.sh \
         -mono -no-fast -pbb -switch semcrisv32f-switch.c \
         -cpu crisv32f -infile 
/home/cagney/PENDING/Werror/src/sim/cris/mloop.in
/bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../../move-if-change 
eng.hin engv10.h
/bin/sh /home/cagney/PENDING/Werror/src/sim/cris/../../move-if-change 
mloop.cin mloopv10f.c
mv: cannot stat `mloop.cin': No such file or directory
gmake[2]: *** [stamp-v10fmloop] Error 1


> On Sun, 1 May 2005, Andrew Cagney wrote:
> 
> 
>>As part of getting ready for GCC 4, I've found that a number of arches
>>don't build with gcc-3.4 when using gdb_mbuild.sh.  As an aid, and to
>>stop me and presumably others from going round in circles, I've updated
>>the MAINTAINERS file to both reflect current reality note the problem.
> 
> 
> Eh... What is your current reality and why don't I see the
> problem you see for cris-elf that warrants marking it as broken?
> 
> There was a build issue before for sim/cris, but it's been fixed
> to the best of my knowledge.  (FWIW in a hackish way, but with
> the same effect to the generated sim/cris files as a proper fix.
> The proper fix has been ok'd by fche FWIW, I just haven't
> regened all CGEN files for all other simulators and tested them;
> it's kind of low-priority.)  That issue seems to match what you
> allude to by "(sim/cris/modelv10.c:4181
> crisv10f_engine_run_full?)"
> 
> I build sim/cris just now (beware, cutnpaste with wrapping):
> /tmp/hptmp/src/configure --target=cris-axis-elf && make all
> ... in short, no problems.
> 
> I also built with gdb_mbuild.sh same host, no problems:
> ...
> cris-elf ...
> ... /tmp/hptmp/src/configure --target=cris-elf --enable-gdb-build-warnings=,-Werror --enable-sim-build-warnings=,-Werror
> ... make cris-elf
> ... run cris-elf
> ... cleanup cris-elf
> ... cris-elf built
> ...
> 
> Of course, that was with this obvious patch to make
> gdb_mbuild.sh build cris-elf (at least it *seemed* necessary):
> 
> --- /home/hp/combined/src/src/gdb/MAINTAINERS	Mon May  9 21:45:37 2005
> +++ ./MAINTAINERS	Tue May 10 03:23:30 2005
> @@ -67,8 +67,7 @@ the native maintainer when resolving ABI
>  	avr		--target=avr ,-Werror
>  			Theodore A. Roth	troth@openavr.org
> 
> -	cris		--target=cris-elf broken
> -			(sim/cris/modelv10.c:4181 crisv10f_engine_run_full?)
> +	cris		--target=cris-elf ,-Werror
> 
>  	d10v		OBSOLETE
> 
> 
> And that's a gcc-3.4 on a i686:
> hydra-13:hp:~: rpm -q gcc
> gcc-3.4.2-6.fc3
> hydra-13:hp:/tmp/hptmp/obj: gcc -v
> Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.2/specs
> Configured with: ../configure --prefix=/usr
> --mandir=/usr/share/man --infodir=/usr/share/info
> --enable-shared --enable-threads=posix --disable-checking
> --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
> 
> I've also build with the configure line above (in a gcc-combined
> tree) on x86_64-unknown-linux-gnu (FC4t2, which uses a
> gcc-4.0-derivate: gcc-4.0.0-2). No problems.  Same thing on i686
> FC2, (gcc-3.3.3-7) no problems.
> 
> What problem do you see and on what host, and have you updated
> since Mar 24 with no local patches, at least none related to the
> cris-elf build issue mentioned above?
> 
> brgds, H-P
>