Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

The race to GCC 3



On Fri, 2002-09-27 at 17:27, Derek D. Martin wrote:

[snip]

> As memory serves, many people said the 6.0 beta was excellent, but the
> 6.0 release was initially atrocious...

  Let me rephrase.  I have it on good authority that the 'final' release
*is* good.  But inevitably, many people will dislike the direction Red
Hat is going.  And, of course, there will be bugs discovered.  What
matters is expeditious updates to fix real problems.  Recent (at a
minimum) history shows Red Hat to pretty good at releasing updates in a
timely fashion.  Time will tell that carries forward with 8.0 and
onward.
  One word of caution that Red Hat will inevitably (and, IMNSHO,
unjustifiably) get a lot flak for.  Binary only modules *will* have
problems if they are not recompiled with gcc 3.x.  (This most
*definitely* includes the Lucent winmodem drivers.) The new modutils
will pick up on this and refuse to load the module.  For those who
distribute binary only modules, the responsibility falls squarely on
them, not Red Hat, or any other Linux distributor, to make things work
with the new kernel/compiler.  I'll dig up what Alan Cox posted to some
of the public Red Hat mailing lists, if anyone is interested, but I
won't have access to email again until Sunday, so I won't get to it
until then.

-- 
-Paul Iadonisi
 Senior System Administrator
 Red Hat Certified Engineer / Local Linux Lobbyist
 Ever see a penguin fly?  --  Try Linux.
 GPL all the way: Sell services, don't lease secrets





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org