caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: William Chesters <williamc@paneris.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Segv while compiling ocaml-3.04
Date: Fri, 21 Dec 2001 10:25:52 +0100 (CET)	[thread overview]
Message-ID: <15395.32.822225.243126@beertje.william.bogus> (raw)
In-Reply-To: <20011221092252.B6254@hars>

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! ***
 > 
 >         GCC 2.96 IS NOT AND WILL NOT BE SUPPORTED BY US !
 > 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

    http://www.linuxworld.com/site-stories/2001/1214.mplayer.html

"... 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


  parent reply	other threads:[~2001-12-21  9:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14  8:39 Christophe Raffalli
2001-12-14 13:25 ` Pixel
     [not found] ` <15385.61778.52293.648002@gargle.gargle.HOWL>
     [not found]   ` <3C1A07E9.B01890D5@univ-savoie.fr>
     [not found]     ` <15386.19382.239731.32280@hector.lesours>
2001-12-15 10:32       ` Christophe Raffalli
2001-12-20 10:50 ` Xavier Leroy
2001-12-20 11:00   ` Christophe Raffalli
2001-12-20 22:49   ` Ian Zimmerman
2001-12-21  8:22     ` Florian Hars
2001-12-21  8:28       ` Ian Zimmerman
2001-12-21  9:25       ` William Chesters [this message]
2001-12-21 10:00         ` Sven
2001-12-21  8:24     ` Luc Maranget
     [not found] <200112170931.KAA0000003112@beaune.inria.fr>
2001-12-17  9:02 ` Christophe Raffalli
2001-12-21 13:01   ` Xavier Leroy
2001-12-22 14:44     ` Pixel
2001-12-23  8:37       ` Xavier Leroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15395.32.822225.243126@beertje.william.bogus \
    --to=williamc@paneris.org \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).