public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Wehle <john@feith.com>
To: imarkov@cs.ucla.edu
Cc: 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: <199908042256.SAA21588@jwlab.FEITH.COM> (raw)
Message-ID: <19990831232000.JbDWxEkIklrgiYMBIGkaAs9ERKMW2d0ribhFzONy1tU@z> (raw)

>   thanks... what you are saying makes sense, but my
> main suggestion was that egcs maintainers consider
> ensuring the availability of good RPMs. This may 
> include contacting someone who can pack RPMs, or
> learning the RPM tricks or... talking to RedHat,
> whatever. Please do not consider this as "making
> binaries for every trashy system", but rather
> "ensuring the utility to major customers".

A very understandable suggestion clearly stated,
unfortunately the wording on early emails seemed
a little harsh and not as clear.

  1) The RPMs tend to quickly get very platform specific
     which means that it's a very big matrix to support.
     The gcc maintainers are concerned that good RPMs
     are available, however they expect the bulk of the
     responsibility for this to be handled by each OS vendor
     since the OS vendor knows best how to configure
     the software for their system.

  2) Since the gcc maintainers release a source code product
     which anyone can use and / or distribute (as long as the
     copyright is respected), it's difficult for them to act
     as police and prevent RPMs which are not appropriate for
     some people to be placed on ftp sites.  Keep in mind that
     they are somewhat understaffed and overworked as it is ...
     and quite frankly it's not their job.

I expect that RedHat will at some point release
a RPM which will work for you.  Unfortunately it
sounds like what you grabbed wasn't released by
RedHat for your platform.  If it's urgent that
you have the new release *now* then you can:

  1) Try random RPMs and contact whoever built
     the RPM for help.

  2) Try building gcc 2.95 from the original source
     code.  If you run into problems then follow the
     instructions for reporting a bug and someone
     probably will try to help out.

  3) Find / hire someone to help you in this endeavor.

Sorry I can't be of more help (my only RedHat development
system at the moment is 5.2 and it's awaiting a new motherboard).

-- John
-------------------------------------------------------------------------
|   Feith Systems  |   Voice: 1-215-646-8000  |  Email: john@feith.com  |
|    John Wehle    |     Fax: 1-215-540-5495  |                         |
-------------------------------------------------------------------------

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

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-04 15:56 John Wehle [this message]
1999-08-31 23:20 ` John Wehle
  -- strict thread matches above, loose matches on Subject: below --
1999-08-06 12:04 Putney, Jeff
1999-08-31 23:20 ` Putney, Jeff
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: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=199908042256.SAA21588@jwlab.FEITH.COM \
    --to=john@feith.com \
    --cc=gcc@egcs.cygnus.com \
    --cc=imarkov@cs.ucla.edu \
    /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).