English version
Accueil     À propos     Téléchargement     Ressources     Contactez-nous    

Ce site est rarement mis à jour. Pour les informations les plus récentes, rendez-vous sur le nouveau site OCaml à l'adresse ocaml.org.

Browse thread
[Caml-list] Segv while compiling ocaml-3.04
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2001-12-21 (09:26)
From: William Chesters <williamc@p...>
Subject: Re: [Caml-list] Segv while compiling ocaml-3.04
Florian Hars writes:
 > On Thu, Dec 20, 2001 at 02:49:17PM -0800, Ian Zimmerman wrote:
 > > Is it worth polluting the source for the sake of an out-and-out vendor
 > > bug?  I'd say no.
 > There is a clean solution to this problem, as implemented in the
 > configure-script of mplayer [...]
 >   if test "$cc_verc_fail" ; then
 >     cat <<EOF
 > *** Please downgrade/upgrade C compiler to gcc-2.95.x or gcc-3.x version! ***
 > EOF
 >     die "Bad gcc version"

Luckily the ocaml team are much too sensible to go this way.  For
those who are tempted, take a look at


"... boorish developers who think of themselves as a sort of
intellectual jeunesse doree ... The attitude I mentioned earlier was
noticeable in the comments on the project's page at freshmeat, ... in
the MPlayer team's remarks about gcc 2.96 ... Actually, the team's
infamous anti-Red Hat rhetoric has been toned down slightly. At Red
Hat's request, some false statements the developers made about 2.96
have been removed from MPlayer's Web site. The team still lets you
know at every opportunity what they think of Red Hat, which gets
tiresome fast."

Basically this approach is absolutely guaranteed to give the
impression that you are over-fussy, arrogant, inconsiderate of real
users' needs etc.  RedHat is too big to ignore and get away with it:
every time they pull some stunt like this, lots of developers waste
lots of time and credibility attempting to convince users that it's
All Red Hat's Fault---eventually succeeding only to discover that the
users still blame them not RH.

My &euro;1E-2.
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr