On Mon, Oct 14, 2002 at 11:26:17PM -0700, Mark Mitchell wrote:
>
> >I'll leave it to our release manager to decide if this issue warrants
> >backporting the relevant patches or not.
>
> I think that your point that we will include the generated files on the
> branch is a good one; let's not backp
I'll leave it to our release manager to decide if this issue warrants
backporting the relevant patches or not.
I think that your point that we will include the generated files on the
branch is a good one; let's not backport the patches given that.
--
Mark Mitchell[EMAIL PROTECTED]
> From: Matthias Klose
>
> Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
> back to bison-1.35 works. HEAD does work well using bison-1.50
>
> cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
> if bison -o c-p$$.c c-parse.y; then \
> test -f c-p$$.output && mv -f c-p
> From: Matthias Klose
>
> Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
> back to bison-1.35 works. HEAD does work well using bison-1.50
>
> cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
> if bison -o c-p$$.c c-parse.y; then \
> test -f c-p$$.output && mv -f c-p
Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
back to bison-1.35 works. HEAD does work well using bison-1.50
cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
if bison -o c-p$$.c c-parse.y; then \
test -f c-p$$.output && mv -f c-p$$.output c-parse.output ; \
mv -f c-p$$.c c-p
5 matches
Mail list logo