public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Putney, Jeff" <jputney@networkmanagementinc.com>
To: gcc@egcs.cygnus.com
Subject: RE: Illegal instruction (core dumped) on i586
Date: Tue, 31 Aug 1999 23:20:00 -0000	[thread overview]
Message-ID: <76EBA0999931D311926C009027557B56349641@iris.nmsmn.com> (raw)
Message-ID: <19990831232000.SsrxbS0SiN92aBLIjM1R-WDjBD_EAvROjc8MIPzOkss@z> (raw)

So some yahoo really thinks gcc should be distributed as source and RedHat
RPMs?  Why redhat?  Why not distribute binaries as solaris packages, or
HP/UX packages, or AIX packages, or DG/UX packages and let's have them do
packages for Slackware and Debian, and all the other linux distrobutions
while we're asking.  Then, while we are on a roll, let's have them do a
package for each of those OS's for each distrobution for each architecture
they run on.  
Linux will run on the palm pilot, don't forget to make a distrobution for
that.
Oh, wait, we need different packages depending on library versions, and type
of assembler and linker.
So, why single out RedHat on an x86?  Is there really a that much greater
density of stupidity on that particular platform.  If so, what does a group
of compiler hackers have to gain from such a group by catering to them?  A
bunch of bug reports because the compiler wouldn't fix their syntax errors
for them and moronic code examples to point to and laugh at is about the
only payback they would get.

--jeff (not the Law, but a jeff of a different flavor)

             reply	other threads:[~1999-08-31 23:20 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-06 12:04 Putney, Jeff [this message]
1999-08-31 23:20 ` Putney, Jeff
  -- strict thread matches above, loose matches on Subject: below --
1999-08-05 12:34 Ram'on Garc'ia Fern'andez
1999-08-31 23:20 ` Ram'on Garc'ia Fern'andez
1999-08-04 17:42 Mike Stump
1999-08-31 23:20 ` Mike Stump
1999-08-04 15:56 John Wehle
1999-08-31 23:20 ` John Wehle
1999-08-04 15:41 Beardsley, Jason
1999-08-31 23:20 ` Beardsley, Jason
1999-08-04 15:13 John Wehle
1999-08-04 15:22 ` Igor Markov
1999-08-04 18:12   ` Benjamin Scherrey
1999-08-31 23:20     ` Benjamin Scherrey
1999-08-05  5:00   ` Steven W Orr
1999-08-05  7:42     ` Joe Buck
1999-08-05  8:04       ` craig
1999-08-05  8:12         ` Daniel Jacobowitz
1999-08-31 23:20           ` Daniel Jacobowitz
1999-08-31 23:20         ` craig
1999-08-31 23:20       ` Joe Buck
1999-08-31 23:20     ` Steven W Orr
1999-08-05  7:49   ` Philipp Thomas
1999-08-31 23:20     ` Philipp Thomas
1999-08-31 23:20   ` Igor Markov
1999-08-31 23:20 ` John Wehle
1999-08-04 13:58 IGOR LEONIDOVICH MARKOV
1999-08-04 14:46 ` Jeffrey A Law
1999-08-31 23:20   ` Jeffrey A Law
1999-08-31 23:20 ` IGOR LEONIDOVICH MARKOV
1999-08-04 13:47 IGOR LEONIDOVICH MARKOV
1999-08-04 14:04 ` Steven W Orr
1999-08-04 14:10   ` Igor Markov
1999-08-04 14:17     ` Steven W Orr
1999-08-04 14:35       ` Igor Markov
1999-08-04 15:01         ` Alex Buell
1999-08-31 23:20           ` Alex Buell
1999-08-04 17:01         ` Joe Buck
1999-08-31 23:20           ` Joe Buck
1999-08-31 23:20         ` Igor Markov
1999-08-31 23:20       ` Steven W Orr
1999-08-04 14:41     ` Robert Lipe
1999-08-04 15:17       ` Igor Markov
1999-08-04 16:48         ` Joe Buck
1999-08-04 16:55           ` Igor Markov
1999-08-04 17:05             ` Jeffrey A Law
1999-08-31 23:20               ` Jeffrey A Law
1999-08-05  7:49             ` Philipp Thomas
1999-08-31 23:20               ` Philipp Thomas
1999-08-31 23:20             ` Igor Markov
1999-08-31 23:20           ` Joe Buck
1999-08-05 10:06         ` David O'Brien
1999-08-31 23:20           ` David O'Brien
1999-08-31 23:20         ` Igor Markov
1999-08-31 23:20       ` Robert Lipe
1999-08-31 23:20     ` Igor Markov
1999-08-31 23:20   ` Steven W Orr
1999-08-04 14:08 ` Joe Buck
1999-08-04 14:13   ` Igor Markov
1999-08-31 23:20     ` Igor Markov
1999-08-31 23:20   ` Joe Buck
1999-08-31 23:20 ` IGOR LEONIDOVICH MARKOV

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=76EBA0999931D311926C009027557B56349641@iris.nmsmn.com \
    --to=jputney@networkmanagementinc.com \
    --cc=gcc@egcs.cygnus.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).