Sigbjorn Finne writes:
>
> Stefan Westmeier writes:
> > Hi,
> >
> > last week someone here at our department installed a new gcc. We used
> > to have 2.7.2.x and we have now 2.8.1. Suddenly our sources we
> > compiled with ghc-2.10, ghc-3.00-1 and ghc-3.01 crashed. OK.
> >
> > The old
Stefan Westmeier writes:
> Hi,
>
> last week someone here at our department installed a new gcc. We used
> to have 2.7.2.x and we have now 2.8.1. Suddenly our sources we
> compiled with ghc-2.10, ghc-3.00-1 and ghc-3.01 crashed. OK.
>
> The old gcc can still be called as gcc.o. Exchanging gcc w
Hi,
last week someone here at our department installed a new gcc. We used
to have 2.7.2.x and we have now 2.8.1. Suddenly our sources we
compiled with ghc-2.10, ghc-3.00-1 and ghc-3.01 crashed. OK.
The old gcc can still be called as gcc.o. Exchanging gcc with gcc.o in
the ghc driver fixed this p
