Bug 633646

Summary:	New nasm 2.09 cause build problems on i386/i686 machines
Product:	[Fedora] Fedora	Reporter:	Alex Lancaster <alex>
Component:	nasm	Assignee:	Adam Tkac <atkac>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	atkac, npajkovs, ovasik
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:	nasm-2.09.02-1.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-30 06:07:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Lancaster 2010-09-14 05:37:26 UTC

When building xbmc on f14 in mock or in the RPM Fusion build system, versions of nasm >= 2.09 causes problems on i686 machines:

make[1]: Entering directory `/builddir/build/BUILD/xbmc-Dharma_beta1/xbmc/cores/paplayer/SPCCodec/SNES/SNESAPU'
nasm -Xvc -DLINUX -O1 -f elf -o SPC700.o SPC700.Asm
SPC700.Asm(328) : error: `%assign' expects a macro identifier
SPC700.Asm(328) : error: `%assign' expects a macro identifier
SPC700.Asm(377) : error: `%assign' expects a macro identifier
SPC700.Asm(377) : error: `%assign' expects a macro identifier
SPC700.Asm(377) : error: `%assign' expects a macro identifier
SPC700.Asm(440) : error: `%assign' expects a macro identifier
SPC700.Asm(481) : error: interminable macro recursion
SPC700.Asm(481) : error: `%xdefine' expects a macro identifier
SPC700.Asm(481) : error: interminable macro recursion
SPC700.Asm(481) : error: `%xdefine' expects a macro identifier
SPC700.Asm(806) : error: `%assign' expects a macro identifier

full log is here:


http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_free/8078-xbmc-10.0-0.12.Dharma_beta1.fc14/i686/build.log

This did not happen with builds with 2.08 and lower with the identical tarball e.g.:

http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_free/7978-xbmc-10.9-0.11.Dharma_beta1.fc14/i686/build.log

Comment 1 Alex Lancaster 2010-09-14 05:38:34 UTC

list of packages installed in last successful build:

http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_free/7978-xbmc-10.9-0.11.Dharma_beta1.fc14/i686/root.log

shows version:  nasm-2.08.02-1.fc14.i686

Comment 2 Alex Lancaster 2010-09-14 22:07:08 UTC

Not sure if this is the same bug, but it seems that this might have been fixed upstream, not sure it's yet made it's way into the 2.09.01 in f14:

https://sourceforge.net/tracker/?func=detail&aid=3026808&group_id=6208&atid=106208

Comment 3 Alex Lancaster 2010-09-14 22:07:32 UTC

See also discussion at:

http://forum.nasm.us/index.php?PHPSESSID=40iat8sdidcadt0t42rv7tfrn0&topic=883.msg3020#msg3020

Comment 4 Alex Lancaster 2010-09-15 00:15:29 UTC

I reported this upstream at:

http://sourceforge.net/tracker/?func=detail&aid=3066383&group_id=6208&atid=106208

Comment 5 Adam Tkac 2010-09-15 12:25:46 UTC

(In reply to comment #4)
> I reported this upstream at:
> 
> http://sourceforge.net/tracker/?func=detail&aid=3066383&group_id=6208&atid=106208

Thanks. I checked 2.09.01 version and problem is still present there. When upstream fixes this issue I will release update for Fedora.

Comment 6 Fedora Update System 2010-09-20 07:02:59 UTC

nasm-2.09.02-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/nasm-2.09.02-1.fc14

Comment 7 Fedora Update System 2010-09-20 18:42:19 UTC

nasm-2.09.02-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update nasm'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/nasm-2.09.02-1.fc14

Comment 8 Fedora Update System 2010-09-30 06:07:32 UTC

nasm-2.09.02-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.