First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 30345
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: media-video herd <media-video@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Shane Simmons <regeya@earthlink.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 30345 depends on: Show dependency tree
Bug 30345 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-10-04 13:22 0000
For whatever reason, mjpegtools on this system always uses '-mcpu=i686 
-march=i686'.  Wouldn't be that big of a deal except that this machine's processor is a 
VIA C3-1G, the bastard cousin of the K6.  For whatever reason, the configure script 
has also decided that cmov support should be enabled, which isn't in the C3-1G's 
instruction set (cmov is an optional instruction.) 
 
This causes a number of "unexplainable" mpeg2enc/etc. crashes. 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Alan 2003-10-15 09:58:00 0000 -------
I have also just seen this in the latest stable build (1.6.1.90-r1).

------- Comment #2 From Christian Jiresjö 2003-11-17 05:06:15 0000 -------
As far as i can see configure never actually checks for the precence of the
instruction but rather just checks if --disable-cmov was given and then
disables it. mpcu/march comes from checking if cmov is enable and if enable do
uname -m and then based on it set mpcu/march else set it to i586.

It should maybe have something like what is described in this gcc-maillinglist
message (http://gcc.gnu.org/ml/gcc-patches/2003-09/msg00217.html)

------- Comment #3 From Wout Mertens (RETIRED) 2004-01-16 04:17:25 0000 -------
In that case, it should just be a matter of

grep -q cmov /proc/cpuinfo || myconf="$myconf --disable-cmov"

But maybe the whole flag generation part of the configuration should be removed and replaced with the user CFLAGS...

------- Comment #4 From Wout Mertens (RETIRED) 2004-01-16 09:20:01 0000 -------
Applied this and version bumped. Please test, and reopen if not working.

First Last Prev Next    No search results available      Search page      Enter new bug