On Fri, 4 May 2007, John Klos wrote:

> I am very excited to hear that other people have successfully self built src 
> on VAX. I tried, but I'm running into this issue still. It's the latest 
> current from the 29th:
...
> if [ xinfo = xinfo ]; then \
>        /usr/tools/bin/nbmakeinfo --no-split -I . -I 
> /usr/src/tools/gcc/../../gnu/dist/gcc4/gcc/doc \
>                -I /usr/src/tools/gcc/../../gnu/dist/gcc4/gcc/doc/include -o 
> doc/gccint.info /usr/src/tools/gcc/../../gnu/dist/gcc4/gcc/doc/gccint.texi; \
> fi
> [1]   Segmentation fault (core dumped) /usr/tools/bin/n...
> nbgmake[1]: *** [doc/gccint.info] Error 139
> nbgmake[1]: Leaving directory `/usr/obj/tools/gcc/build/gcc'
>
>
> Any ideas?

   Is the gcc compiler on the vax (specifically /usr/libexec/cc1) also from 
those same sources?  The symptom you describe was fixed by revision 1.11 
of gnu/dist/gcc4/gcc/config/vax/vax.md.  Building tools natively on the 
vax uses the native gcc to build the makeinfo tool, and prior to that 
version of vax.md, the wrong code was getting generated during the build 
of makeinfo.  You can check if this was the problem by disassembling 
tools/texinfo/build/makeinfo/index.o and look for movc3 instructions in 
cm_printindex.  The third one would look like 'movc3 $0x30,*0x0(r6),(r6)' 
if it's bad. [That was copied from my 4.0 build without that fix to the 
4.0 source tree, which I working on getting the appropriate fixes pulled 
up to fix.]

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA