Bug 159498 – media-libs/xvid-1.1.0-r3 build fail with dev-lang/yasm-0.5.0

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Shunichi Fuji 2006-12-30 10:45:48 UTC]

xvid configure script prefer to use yasm than nasm.
if yasm and nasm installed on system, configure select yasm.

apply xvid-1.1.0-noexec-stack.patch spawn failur compiling at asm code on x86 system at least for x86 (i686-pc-linux-gnu).
becaue this patch include incompatible with yasm on x86 code.

In contrast, build succeed while taking off this patch.

...Error log...
  C: utils/mem_transfer.c
  C: utils/timer.c
  A: bitstream/x86_asm/cbp_3dne.asm
../../src/bitstream/x86_asm/cbp_3dne.asm:130: invalid argument to [SECTION]
../../src/bitstream/x86_asm/cbp_3dne.asm:130: undefined symbol `.note.GNU' (first use)
../../src/bitstream/x86_asm/cbp_3dne.asm:130: undefined symbol `stack' (first use)
../../src/bitstream/x86_asm/cbp_3dne.asm:130:  (Each undefined symbol is reported only once.)
make: *** [bitstream/x86_asm/cbp_3dne.o] Error 1

[Comment 1 Shunichi Fuji 2006-12-31 11:49:30 UTC]

oops, i confirmed success compiling with yasm-0.5.0_rc1.
is there something wrong in yasm or does yasm get newer incompatibly?

it also occured in libsdl.

[Comment 2 Christian Faulhammer (RETIRED) 2007-01-24 07:35:20 UTC]

amd64 and/or Kugelfang, could you please take a look too at this problem?

[Comment 3 Alexis Ballier 2007-01-26 08:10:16 UTC]

*** Bug 163750 has been marked as a duplicate of this bug. ***

[Comment 4 Alexis Ballier 2007-01-26 08:13:15 UTC]

This still applies to xvid 1.1.2 and is due to the execstack patch.
Is that a regression in yasm or is the patch using a deprecated syntax ?

[Comment 5 SpanKY 2007-01-26 08:14:11 UTC]

if you quote the section name, it should work in both nasm and yasm

 %ifidn __OUTPUT_FORMAT__,elf
-section .note.GNU-stack noalloc noexec nowrite progbits
+section ".note.GNU-stack" noalloc noexec nowrite progbits
 %endif

the latest version of yasm in svn doesnt suck and supports section names like this without quotes, but that isnt released so just quote it for now

[Comment 6 Alexis Ballier 2007-01-26 10:37:49 UTC]

Thanks for the heads up.

vapier (and/or others) : could you please update the patch then for xvid-1.1.2 (adding a new bziped patch named with -1.1.2 replacing the current one should avoid md5 problems).
yasm 0.5.0 is in ~arch so leaving 1.1.0-r3 as is shouldn't be a problem for now.

I'd have done this myself but I'm at work right now and I'll be away for the week end. I'll do it on monday if this is not fixed yet at that time.

[Comment 7 SpanKY 2007-01-26 11:08:57 UTC]

erm, i dont see what yasm status has to do with this ... no yasm release has ever support non-ascii chars in section names without quoting

so we need to update all xvid ebuilds as this failure should [in theory] happen whenever user has yasm installed on x86

[Comment 8 SpanKY 2007-01-27 11:09:31 UTC]

ive fixed 1.1.0-r3 and 1.1.2 since that covers the latest amd64/x86 stable/unstable