gcc-20010409 compilation fails on Tru64 Unix

[Per Wigren]

Ok, I just HAD to try again... ;-)

I did a HEAD checkout, but now both hunks failed...

bash-2.05# gpatch -p0 < /tmp/gcc-patch 
patching file aclocal.m4
patching file configure.in
Hunk #1 FAILED at 349.
Hunk #2 FAILED at 437.
2 out of 2 hunks FAILED -- saving rejects to file configure.in.rej
bash-2.05#

Should I use another branch than HEAD? How do I "downgrade"? (I'm not very 
familiar with CVS - I just do cvs up -dP and cvs co :)
When will this patch (patches) be committed to CVS?

Regards
Per Wigren

onsdag 11 april 2001 23:09 skrev Rainer Orth:
> > bash-2.05# rm -rf gcc-20010409/
> > bash-2.05# gtar xfz ../gcc-20010409.tar.gz
> > bash-2.05# cd gcc-20010409/gcc/
> > bash-2.05# gpatch -p0 < /tmp/gcc-patch
> > patching file aclocal.m4
> > patching file configure.in
> > Hunk #2 FAILED at 437.
> > 1 out of 2 hunks FAILED -- saving rejects to file configure.in.rej
> > bash-2.05#
>
> strange: either a problem with the snapshot or a broken gpatch:
>
> % cvs -q update -p -rgcc_ss_20010409 configure.in > ~/configure.in
> % cvs -q update -p -rgcc_ss_20010409 aclocal.m4 > ~/aclocal.m4
> % cd
> % patch -s -p0 < bool.patch
> %
>
> I vaguely recall that there for some time the CVS repository was messed up,
> mixing files from branch and trunk.  Maybe the snapshot was cut during this
> period.  Please compare configure.in in the snapshot with the repository
> version.
>
> And compare the .rej file with the original configure.in, maybe you can see
> why it doesn't apply.
>
> 	Rainer
>
> ---------------------------------------------------------------------------
>-- Rainer Orth, Faculty of Technology, Bielefeld University
>
> Email: ro@TechFak.Uni-Bielefeld.DE