Skip to content
New issue
Jump to bottom

MPlayer fails to start in PC pool with illegal instruction #312

Closed
pmenzel opened this issue Mar 8, 2017 · 0 comments · Fixed by #332
Closed

MPlayer fails to start in PC pool with illegal instruction #312

pmenzel opened this issue Mar 8, 2017 · 0 comments · Fixed by #332

Comments

@pmenzel
Copy link
Collaborator

pmenzel commented Mar 8, 2017

Currently MPlayer cannot be started on any system in the PC pool.

For example on sigchld:

[  171.675370] traps: mplayer[1249] trap invalid opcode ip:561cade7dc60 sp:7ffc93847320 error:0
[  171.675373]  in mplayer[561cadc52000+1032000]

Probably, the MPlayer (or FFmpeg) is optimized in a way, that all features of the build host are activated, not present on other systems. Maybe some compatibility flags have to be passed.
david added a commit that referenced this issue Mar 27, 2017
@david
New Revision: MPlayer
6f6f2ed 
new configure option for Issue#312

fixed #312
@david david mentioned this issue Mar 27, 2017
Merged
pmenzel pushed a commit that referenced this issue Mar 27, 2017
@david @pmenzel
mplayer: Detect CPU type at run-time
9cb21dd 
Configure the MPlayer build to detect the CPU type at run-time.

Fixes: #312
Sign in to join this conversation on GitHub.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Let MPlayer detect CPU at run-time mariux64/bee-files
1 participant
@pmenzel