Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 4609 - RPM software upgrade by RedHat for 486+
RPM software upgrade by RedHat for 486+
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-08-19 11:10 EDT by etienne.lorrain
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-19 11:31:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description etienne.lorrain 1999-08-19 11:10:37 EDT

  Is that just me or the latest upgrade for
 rpm (rpm-3.0.2-6.0.i386.rpm) is compiled
 for i486+, i.e. my 386 is too old to get
 RedHat 6.0 with its updates?
 Shouldn't it be named "rpm-3.0.2-6.0.i486.rpm"

  It produces an "invalid instruction exception"
 as soon as you request anything else than --help.

Comment 1 Jeff Johnson 1999-08-19 11:31:59 EDT
All Red Hat 6.0 packages, not just rpm, have this problem at the
moment. For 3 years, rpm has supplied optflags as -m486 which
meant "Permit i486 instruction scheduling but don't use i486
instructions." EGCS silently changed to permit i486 instructions
also. This was realized too late in the Red Hat 6.0 release cycle to
recompile all packages. The compiler in our 6.0 build system
has just been upgraded to one with the original -m486 semantics
(the egcs package from Raw Hide) so the problem will not occur
in the future. Howvere, all packages produced by the Red Hat 6.0
egcs will continue to use 486 instructions.

If you're on a i386 you will have to recompile from src.rpm's using
the egcs package from Raw Hide.

Note You need to log in before you can comment on or make changes to this bug.