Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-October/009934.html below:

[Python-Dev] gcc versions (was:RE: Possible bug (was Re: some other junk, ...))

• Previous message: [Python-Dev] gcc versions (was:RE: Possible bug (was Re: some other junk, ...))
• Next message: Mandrake vs glibc (was RE: [Python-Dev] RE: Possible bug (was Re: numpy, overflow, inf, ieee, and rich comparison)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Charles G Waldman writes:
 > AFAIK, this version of GCC was never "blessed" by the GCC maintainers
 > and should not be being used for any production work.  I think
 > Mandrake did a bad thing by shipping this version.  Not quite as bad

  I agree.

 > In any case, I don't think we should put effort into chasing down bugs
 > that are caused by bogus C compilers.  Any reports coming in from
 > RedHat 7.0 users or Mandrake 7.1 need to be evaluated in this light.

  I think Skip & I were showing that there isn't a bug for Mandrake
7.1.  I don't know what version of GCC shipped with Mandrake 7.0,
which may have been the version Tim received the report for (I recall
he said "Mandrake 7", which isn't specific).


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member

• Previous message: [Python-Dev] gcc versions (was:RE: Possible bug (was Re: some other junk, ...))
• Next message: Mandrake vs glibc (was RE: [Python-Dev] RE: Possible bug (was Re: numpy, overflow, inf, ieee, and rich comparison)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4