> The statistics become much higher when you realize that:
> 1. Redhat wants to change the buggy 2.96 compiler (which actually has about
> 5 versions I am ware of that they refuse to admit or tag as different
> versions). 2. Mandrake is compatible to RH (meaning Mandrake want you to be
> able to install Redhat RPMS and therefore have to use the same compiler as
> RH).

Wrong in both terms:

1. GCC 2.96 to me seems very stable these days - and I have more then enough 
compile expirience with it (I use 2.96 only up until few days ago). It had 
few problems when it came out when RH 7.0, 7.1 and with the first version on 
7.2, but if you use gcc-2.96-112 then it should be stable. 

2. Red Hat is definately not compatible with Mandrake any more. Specially with 
Red Hat 8.0 which will be totally incompatible with anything on the market - 
be it kernel modules, or just binary applications. RH 8.0 is using glibc 2.3, 
a kernel which is heavily modified to compile under GCC 3.2 (which is the 
only compiler that Red Hat 8.0 is installing, although gcc2.96 is still on 
the CD) - be my guest, try to install any .i386.rpm from Red Hat 8.0 to 
Mandrake, it's not even compatible with RPM version (4.1.0 now and counting) 
(any company who thinks to start supporting RedHat 8.0 - make sure you have 
enough Aspirin in your closet)

> Actually - what comes out of all this is that Mandrake HAS to release a
> major version whenever RH releases one (or shortly after because of
> development time) if it wants to keep it's objective of staying RH
> compatible. So it's not such a big surprise to me...:). Suse uses RPM too
> but is NOT RH compatible and did not follow suit on the 2.96 issue. They
> are a sane company I guess.

But it's NOT! Mandrake 9 cannot run ANYTHING from Red Hat 8.0 - unless it's an 
noarch RPM ;)

Thanks,
Hetz

================================================================To unsubscribe, send 
mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to