#42672: x264 @20130823_0: build failure on 10.9 using Apple clang --------------------------+----------------------- Reporter: rjvbertin@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: mavericks Port: x264 | --------------------------+----------------------- Changes (by devans@…): * status: new => assigned * version: 2.2.1 => Comment: x264 updated to build 142 (x264 @20140124) in r117551. Please update your ports and try again. -- Ticket URL: <https://trac.macports.org/ticket/42672#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#42672: x264 @20130823_0: universal build failure on Apple clang, i386 issues. --------------------------+----------------------- Reporter: rjvbertin@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: mavericks Port: x264 | --------------------------+----------------------- Changes (by devans@…): * cc: jeremyhu@… (added) Comment: jeremyhu@ committed an additional clang fix in r117575 but that doesn't help this issue either. The issue was recently discussed (heatedly) upstream [https://mailman.videolan.org/pipermail/x264-devel/2014-February/010371.html Failure to build x264 with ASM on i386]. The closing guidance from the upstream developers is this: * give up on --enable-pic as x264's asm optimizations for i386 wouldn't be PIC anyway (even if you didn't get this compilation error) and will have textrels; * give up on asm and use --disable-asm if you for some stupid reason no matter what need PIC; * give up on i386 and build for x86_64 if need both PIC and asm. I don't see any way around the situation either but, of course, I would defer to anyone who has a better idea. In the meantime, in the current state of the port, it is obvious that +asm is incompatible with +universal due to i386 issues. +universal builds successfully without +asm and this is the current default. +asm builds fine for x86_64 without +universal, again the default. I also note that this is not just a Mavericks issue. I can reproduce the problem on ML as well. For now, don't use +asm and +universal together. If you want +asm, use the default build. I am marking variant +asm as conflicting with +universal. -- Ticket URL: <https://trac.macports.org/ticket/42672#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#42672: x264 @20130823_0: universal build failure on Apple clang, i386 issues. --------------------------+---------------------- Reporter: rjvbertin@… | Owner: devans@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: i386 Port: x264 | --------------------------+---------------------- Changes (by devans@…): * status: assigned => closed * keywords: mavericks => i386 * resolution: => fixed Comment: Better solution. +asm variant dropped and --disable-asm asserted whenever configuring for i386. This allows +universal to build with asm optimizations for x86_64 and without for i386. Also fixes -universal build for i386. Other possible archs are handled by the port itself. No ABI impact. See https://lists.macosforge.org/pipermail/macports- users/2014-March/034711.html -- Ticket URL: <https://trac.macports.org/ticket/42672#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X