> --=====================_434647510==_.ALT
> Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>
> >I unpack, hack fix, build in my work tree. When that all works I diff that
> >with the base tree and it to the spec file and try the rpm build
> >
> > Along these lines...am I the only person to lose sleep over gcc
> > upgrades and a failure to compile executables after upgrading from 5.2 to
> > 6.0 and patches?
I also sometimes have problems building 6.0 source rpms for 5.x. Which
reminds me....
According to the docs, I am supposed to be able to build binaries for RHL
5.2 systems on my RHL 6.0 system if I install the compatibility libraries
(which I have). I see not a whisper of how I do it; I'd have thought the
comb\patibility libraries would either have the information, or a pointer
to it. But no, we don't need that, do we?
Where IS the information?
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null