Skip to content

RPM of R-1.2.1 for RH 7?

3 messages · apjaworski@mmm.com, Peter Dalgaard, Martyn Plummer

#
segfaulted
fixed
Here is what the compiler update installed/updated on my machine.

libstdc++-2.96-69
gcc-c++-2.96-69
cpp-2.96-69
gcc-2.96-69
libstdc++-devel-2.96-69
gcc-objc-2.96-69
gcc-g77-2.96-69

The g77 is there but I do not know what the changes to it were.  All I know
is that on my Linux box (266MHz Pentium MMX, generic MB and video card)
this compiler compiled the whole R-1.2.1 distribution with no problems.
(This included the g77 compilations.)  All tests passed.  I could also
compile and check several packages.  Moreover, I could compile the Matrix
package with no problems, whereas I had problems with it using gcc-2.95.2

 As Prof. Ripley remarked, the gcc-2.96 compiler suite is not an official
release.   The 2.95.2 is recommended for production work.  The 2.96 version
is reported to have problems with C++ code but I could not verify that
these problems were fixed in the upgrade.  Again, I know that I can
compile, for example, the whole QT-2.2.2 tutorial without a single warning,
but this of course does not prove anything.

Cheers,

Andy

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-help-request at stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
#
apjaworski at mmm.com writes:
Yup. Even though Brian (and many otheres with him) is right that
RedHat pulled a terrible stunt with this compiler-"release", they seem
to have landed the thing on its feet, not least due to very bright
people like Jakub Jelinek who have been handling the reports of
compiler bugs we triggered entirely sensibly.

(I still remember the bug in the "cb" C beautifier program which could
turn 1e-6 into 1e - 6 which the complier parsed as 1 - 6 = -5.  I
reported that one to HP only to find it again years later in Solaris
based on the same codebase...)
#
On 23-Jan-01 Peter Dalgaard BSA wrote:
This is a little off-topic but I would like to say my piece.

I would like to echo Peter's praise of Jakub, who has not only been very
efficient in fixing these bugs but also remained polite and calm in the
face of considerable hostility.

Don't forget that a lot of ordinary users (myself included) had to track
down these bugs and submit short test programs that Jakub could work with.
Most, if not all, of these users would not normally choose to use such
bleeding-edge software, and there has consequently been a loss of good
will.  This is the heart of the problem: Red Hat broke one of the many
rules of etiquette in the open source community by releasing gcc 2.96.
Only the gcc development team is responsible for deciding when gcc is
ready for general use, and the same is true for all the other components
of a GNU/Linux system. If Red Hat don't respect this then they will lose
their user base.

If I may speculate on the reasons why Red Hat pulled this trick, I suspect
that they switched the development version of their distribution to gcc
2.96 thinking that it would have stabilized to gcc 3.0 by the time Red
Hat 7.0 was released. But they were wrong (Current estimate for gcc 3.0 is
end Q1 2001).  The need to generate some revenue from distribution sales
forced them to release 7.0, rather than wait.  This is pure speculation
of course, but it is a scenario that makes them appear rational, if
somewhat optimistic.

Finally I should point out that gcc 2.96 still doesn't compile R
correctly on alpha.

Martyn
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-help-request at stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._