Mailing List Archive: Gentoo: AMD64

mplayer 'illegal instruction'

Index | Next | Previous | View Threaded

raffaele.belardi at st

Jun 5, 2009, 4:51 AM

Post #1 of 8 (1015 views)
Permalink

mplayer 'illegal instruction'

I use the binpkg feature to quickly update an Athlon64 system with
packages compiled on an Athlon64 X2 system. march=athlon64 on both
systems, I avoided using the new gcc 4.3.2 march=native option to
maintain compatibility. The Athlon64 apparently runs fine, but yesterday
I discovered that mplayer aborts with 'illegal instruction', spitting
out a warning that possibly the package was compiled for a different
machine, which is true!

Anybody has ideas why it is happening? On last update I switched from
gcc-4.2.1 to gcc-4.3.2, but since the system seemed stable and running
fine till now I did not do the recommended emerge -e world. Maybe some
mplayer dependency is still referencing the old gcc libraries?

raffaele

volkerarmin at googlemail

Jun 5, 2009, 5:00 AM

Post #2 of 8 (985 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

On Freitag 05 Juni 2009, Raffaele BELARDI wrote:
> I use the binpkg feature to quickly update an Athlon64 system with
> packages compiled on an Athlon64 X2 system. march=athlon64 on both
> systems, I avoided using the new gcc 4.3.2 march=native option to
> maintain compatibility. The Athlon64 apparently runs fine, but yesterday
> I discovered that mplayer aborts with 'illegal instruction', spitting
> out a warning that possibly the package was compiled for a different
> machine, which is true!
>
> Anybody has ideas why it is happening? On last update I switched from
> gcc-4.2.1 to gcc-4.3.2, but since the system seemed stable and running
> fine till now I did not do the recommended emerge -e world. Maybe some
> mplayer dependency is still referencing the old gcc libraries?
>
> raffaele

no, that has nothing to do with old gcc and everything with mplayer using
instructions the athlon64 does not have. Like SSE3

lists at f_philipp

Jun 6, 2009, 3:23 AM

Post #3 of 8 (980 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

Raffaele BELARDI schrieb:
> I use the binpkg feature to quickly update an Athlon64 system with
> packages compiled on an Athlon64 X2 system. march=athlon64 on both
> systems, I avoided using the new gcc 4.3.2 march=native option to
> maintain compatibility. The Athlon64 apparently runs fine, but yesterday
> I discovered that mplayer aborts with 'illegal instruction', spitting
> out a warning that possibly the package was compiled for a different
> machine, which is true!
>
> Anybody has ideas why it is happening? On last update I switched from
> gcc-4.2.1 to gcc-4.3.2, but since the system seemed stable and running
> fine till now I did not do the recommended emerge -e world. Maybe some
> mplayer dependency is still referencing the old gcc libraries?
>
> raffaele
>

I bet you've enabled the ssse3 USE-flag for mplayer. This enabled hand
written assembler code for a CPU feature you don't seem to have.

Attachments:

signature.asc (0.25 KB)

raffaele.belardi at st

Jun 9, 2009, 12:46 AM

Post #4 of 8 (973 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

Florian Philipp wrote:
> Raffaele BELARDI schrieb:
>> I use the binpkg feature to quickly update an Athlon64 system with
>> packages compiled on an Athlon64 X2 system. march=athlon64 on both
>> systems, I avoided using the new gcc 4.3.2 march=native option to
>> maintain compatibility. The Athlon64 apparently runs fine, but yesterday
>> I discovered that mplayer aborts with 'illegal instruction', spitting
>> out a warning that possibly the package was compiled for a different
>> machine, which is true!
>
> I bet you've enabled the ssse3 USE-flag for mplayer. This enabled hand
> written assembler code for a CPU feature you don't seem to have.
>

Nope, both machines have the same make.conf that does not enable sss3.
'euse -a' does not show sss3 on either machine.

BTW, if my understanding is correct, a binpkg's USE flags are checked
against the current USE flags and if there is mismatch the binpkg is
ignored and tha package recompiled from the sources.

raf

lists at f_philipp

Jun 9, 2009, 3:24 AM

Post #5 of 8 (976 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

Raffaele BELARDI schrieb:
> Florian Philipp wrote:
>> Raffaele BELARDI schrieb:
>>> I use the binpkg feature to quickly update an Athlon64 system with
>>> packages compiled on an Athlon64 X2 system. march=athlon64 on both
>>> systems, I avoided using the new gcc 4.3.2 march=native option to
>>> maintain compatibility. The Athlon64 apparently runs fine, but yesterday
>>> I discovered that mplayer aborts with 'illegal instruction', spitting
>>> out a warning that possibly the package was compiled for a different
>>> machine, which is true!
>> I bet you've enabled the ssse3 USE-flag for mplayer. This enabled hand
>> written assembler code for a CPU feature you don't seem to have.
>>
>
> Nope, both machines have the same make.conf that does not enable sss3.
> 'euse -a' does not show sss3 on either machine.
>
> BTW, if my understanding is correct, a binpkg's USE flags are checked
> against the current USE flags and if there is mismatch the binpkg is
> ignored and tha package recompiled from the sources.
>
> raf
>

And ffmpeg?

Attachments:

signature.asc (0.25 KB)

raffaele.belardi at st

Jun 9, 2009, 5:13 AM

Post #6 of 8 (986 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

Florian Philipp wrote:
>>> I bet you've enabled the ssse3 USE-flag for mplayer. This enabled hand
>>> written assembler code for a CPU feature you don't seem to have.
>>>
>> Nope, both machines have the same make.conf that does not enable sss3.
>> 'euse -a' does not show sss3 on either machine.
>>
>
> And ffmpeg?
>

I don't think I have package-specific USE flags, at least for the
mplayer-related ones, if that is what you mean. I'll re-check.

raf

hengenj at rhrk

Jun 9, 2009, 6:00 AM

Post #7 of 8 (971 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

Raffaele BELARDI wrote:
> I don't think I have package-specific USE flags, at least for the
> mplayer-related ones, if that is what you mean. I'll re-check.

Maybe add the use flag cpudetection to mplayer (and maybe also ffmpeg):

$ euse -i cpudetection
global use flags (searching: cpudetection)
************************************************************
no matching entries found

local use flags (searching: cpudetection)
************************************************************
[- ] cpudetection (media-sound/gnusound):
Enables runtime cpu detection

[- ] cpudetection (media-sound/jack-audio-connection-kit):
Enables runtime cpudetection

[- ] cpudetection (media-video/ffmpeg):
Enables runtime cpudetection (useful for bindist, compatability on other
CPUs)

[- ] cpudetection (media-video/mplayer):
Enables runtime cpudetection (useful for bindist, compatability on other
CPUs)

J_M

lists at f_philipp

Jun 9, 2009, 7:01 AM

Post #8 of 8 (970 views)
Permalink

Re: mplayer 'illegal instruction' [In reply to]

Raffaele BELARDI schrieb:
> Florian Philipp wrote:
>>>> I bet you've enabled the ssse3 USE-flag for mplayer. This enabled hand
>>>> written assembler code for a CPU feature you don't seem to have.
>>>>
>>> Nope, both machines have the same make.conf that does not enable sss3.
>>> 'euse -a' does not show sss3 on either machine.
>>>
>> And ffmpeg?
>>
>
> I don't think I have package-specific USE flags, at least for the
> mplayer-related ones, if that is what you mean. I'll re-check.
>
> raf
>

I only ask because recently ssse3 seems to have been the package default
for ffmpeg - if I remember correctly. I don't know whether this has been
reversed.

Attachments:

signature.asc (0.25 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads