Bug 200532 - media-plugins/audacious-plugins-1.4.[01] lacks sse2 USE flag
Bug#: 200532 Product:  Gentoo Linux Version: unspecified Platform: x86
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: chainsaw@gentoo.org Reported By: teknohog+gentoobugz@iki.fi
Component: Ebuilds
URL: 
Summary: media-plugins/audacious-plugins-1.4.[01] lacks sse2 USE flag
Keywords:  
Status Whiteboard: 
Opened: 2007-11-27 17:14 0000
Description:   Opened: 2007-11-27 17:14 0000 
Of my two active Gentoo machines, one has an sse2 capable CPU, and the other
does not. I use least-common-denominator USE/CFLAGS etc. to build binaries for
both machines. Unfortunately, when emerging audacious-plugins on the newer
machine, ./configure autodetects sse2, so the binary crashes with "illegal
instruction" on the older machine. There's currently no USE flag for sse2, and
CFLAGS don't help.

Reproducible: Always

Steps to Reproduce:
1. Emerge audacious-plugins with USE="-sse2" on a sse2 capable machine
2. Emerge the binary on a non-sse2 machine
3. Start audacious on the latter machine, load some music files

Actual Results:  
Illegal instruction

Expected Results:  
Play the music

I've added the sse2 USE flag into the ebuild, along with use_enable sse2. This
fixes the problem for me.

------- Comment #1 From Risto A. Paju 2007-11-27 17:15:22 0000 ------- 
Created an attachment (id=137130) [details]
Fixed ebuild

------- Comment #2 From Jakub Moc (RETIRED) 2007-11-27 19:13:37 0000 ------- 
Reopen with a unified diff and emerge --info attached. Thanks.

------- Comment #3 From Risto A. Paju 2007-11-27 20:49:18 0000 ------- 
Created an attachment (id=137152) [details]
emerge --info

------- Comment #4 From Risto A. Paju 2007-11-27 20:50:54 0000 ------- 
Created an attachment (id=137153) [details]
Add sse2 USE flag to ebuild

------- Comment #5 From Risto A. Paju 2007-11-27 20:51:38 0000 ------- 
Reopened with info and diff as requested.

------- Comment #6 From Tony Vroon 2007-12-03 15:49:48 0000 ------- 
This has been addressed in the audacious-plugins-1.4.2 ebuild that was just
committed to CVS. You will see this in portage within the next two hours.

Thank you for your bug report :)