libvpx OS X 32-bit causes warning about absolute addressing, from asm code.

[GoogleCodeExporter]

A libvpx built on OS X 32-bit (target x86-darwin11-gcc) produces warnings about 
absolute addressing when linking.

What is the expected behavior? What do you see instead?

Expect no warning when linking a 32-bit executable.  Instead, get:

ld: warning: PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not 
allowed in code signed PIE, but used in _vp8_dequant_idct_add_mmx from [install 
path]/libvpx.a(dequantize_mmx.asm.o). To fix this warning, don't compile with 
-mdynamic-no-pic or link with -Wl,-no_pie

The problem occurs even when linking test_libvpx when building libvpx itself

What version are you using? On what operating system?

libvpx-1.4.0, OS X 10.10, Xcode 6.3.1, Yasm 1.3.0.  Also occurs with tip of git 
(commit 623e6eed5e4b1b49c2c73ce0f4d8be6f267e7dbd, Wed May 6 17:29:51 2015 +0000)

Can you reproduce using the vpxdec or vpxenc tools? What command line are
you using?

N/A.  Link time issue.

Please provide any additional information below.

Original issue reported on code.google.com by jonathan...@gmail.com on 6 May 2015 at 9:53

[GoogleCodeExporter]

Original comment by ya...@google.com on 7 May 2015 at 10:18

• Changed state: Assigned

[GoogleCodeExporter]

Tom can you reproduce?

Original comment by fgalli...@google.com on 7 May 2015 at 10:18

[GoogleCodeExporter]

Reproduces on tip of tree. Appears to be an issue with the GET_GOT macro in 
x86_abi_support.asm (or SHADOW/UNSHADOW_ARGS). Anyway, I'm guessing. Assigning 
to Yunqing (fixed the last PIC related issue).

Original comment by tomfine...@google.com on 12 May 2015 at 9:03

[GoogleCodeExporter]

The warnings are gone while configuring with "--enable-pic". Please try it. It 
seems no-PIE build isn't allowed/preferred on OS X.

Original comment by yunqingw...@google.com on 13 May 2015 at 12:09

• Changed state: Started