From: "Steven Bosscher"
The problem doesn't happen on machines I own or have root access to.
It's only a problem when you try to do gcc development on machines
hosted by 3rd parties (SF compile farm, HP cluster, machines at places
where I work and/or where I try to convince people to use gfortr
From: "Joe Buck"
Debian stable, and Ubuntu Hardy (most recent LTS release) have 2.3.1.
Same with OpenSUSE 11.0. So I think 2.3.1 is typical of current stable
releases; Fedora tends to be bleeding edge and not typical.
I still have to deal with older distros (e.g. RHEL 4), but it's
already nec
I'm hoping to integrate GCC with the complex math library MPC. You can read
the gory details here:
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00671.html
To ensure widespread portability, the MPC developers are keeping track of
the platforms where the latest MPC works here:
http://www.loria.fr/
From: "Ian Lance Taylor" <[EMAIL PROTECTED]>
Kaveh mentioned these in his original e-mail, explained why he found
it difficult to fix, and added this to the Makefile so that it
wouldn't break the build.
# bitmap.c contains -Wc++compat warnings.
bitmap.o-warn = -Wno-error
This too should be fix
From: "Richard Guenther" <[EMAIL PROTECTED]>
I support the final-release-then-close approach. But can we get a
volunteer to convert that branch to GPLv3... ?
I strongly object to moving the 4.1 brach to GPLv3.
Richard.
Because... ?
--
Kaveh R. Ghazi
