Illegal instruction (core dumped) on i586

[Steven W Orr]

Sometimes it does work. The problem is that not all rpms are going to be
compatible with all platforms. There might be differences between SUSE,
RH, Debian, Caldera, etc such that the rpm might not work on a platform
that it wasn't built on. In fact, if the rpm doesn't build from src then
that's a good indication that there is a dependency that you are not yet
aware of. Personally, I have my rpm customized so that it produces i686
instructions. If you got the rpm from redhat, then that's an indication
that it was built for *some* sort of red hat system. If you're running
RH6.0 then *usually* you will be able to run rpm's that are specifically
built for 6.0 or are designated as 6.0 update rpms.

BTW, The src install is required in order to do the build. The build
produces the resulting rpms in /usr/src/redhat/RPMS. In this case they
would all end up in the i386 subdirectory.

-- 
----------Time flies like the wind. Fruit flies like a banana.----------------
--------Stranger things have happened but none stranger than this.-------------
Steven W. Orr      steveo@world.std.com     <site of former bang addr:-)>
---------------"Listen to me! We are all individuals."-------------------------

On Wed, 4 Aug 1999, Igor Markov wrote:

=>
=>> Instead you should have gone to /contrib/libc6/SRPMS and fetched
=>> gcc-2.95-2.src.rpm and then
=>> rpm -i gcc-2.95-2.src.rpm
=>> cd /usr/src/redhat
=>> rpm -ba gcc.spec
=>> rpm -Uvh all the resulting i386.rpm files
=>> Then they would have been made for your machine.
=>
=>   wait.. not so fast!
=>   I have a regular Pentium-150 (not an AMD or Cyrix clone),
=>   and downloaded RPMs from the i386 directory.
=>
=>   I understand it's not a hacker thing to download binaries,
=>   but shouldn't that work? (and why do you want me to necessarily
=>   go through the source install)
=>
=>							Igor
=>