Bug 161572 - cannot rebuild valgrind from SRPM
cannot rebuild valgrind from SRPM
Product: Fedora
Classification: Fedora
Component: valgrind (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2005-06-24 11:30 EDT by John Reiser
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 2.4.0-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-12 12:46:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Reiser 2005-06-24 11:30:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
Rebuilding valgrind from SRPM fails with compiler messages:
error: unknown register name 'mm0' in 'asm'

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpm --install valgrind-2.4.0-2.src.rpm
2. cd SPECS; rpmbuild -ba valgrind.spec

Actual Results:       ...
/usr/bin/perl ./gen_insn_test.pl < insn_fpu.def > insn_fpu.c
if gcc -DHAVE_CONFIG_H -I. -I. -I../../..     -Winline -Wall -Wshadow -g -I../../../include -Wno-long-long -Wno-pointer-sign -MT insn_fpu.o -MD -MP -MF ".deps/insn_fpu.Tpo" -c -o insn_fpu.o insn_fpu.c; \
then mv -f ".deps/insn_fpu.Tpo" ".deps/insn_fpu.Po"; else rm -f ".deps/insn_fpu.Tpo"; exit 1; fi
insn_fpu.c: In function 'faddl_1':
insn_fpu.c:383: error: unknown register name 'mm0' in 'asm'
insn_fpu.c: In function 'faddl_2':
insn_fpu.c:421: error: unknown register name 'mm0' in 'asm'
make[5]: *** [insn_fpu.o] Error 1

Expected Results:  Successful build.

Additional info:
Comment 1 John Reiser 2005-06-24 11:31:52 EDT
gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)
Comment 2 Jakub Jelinek 2005-07-12 12:46:20 EDT
valgrind bug.  Fixed in valgrind-2.4.0-3.

Note You need to log in before you can comment on or make changes to this bug.