#30370: libpixman erroneous execution with llvm-gcc-4.2 -----------------------------------------+---------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Keywords: lion llvm-gcc-4.2 cairo pdf | Port: libpixman -----------------------------------------+---------------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => ryandesign@… -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Changes (by eborisch@…): * status: closed => reopened * resolution: fixed => Comment: This fix breaks the universal build on Snow Leopard. (Log attached.) Perhaps change to gcc-4.2 (builds universal successfully) on Snow Leopard and clang on Lion? -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Comment(by ejtttje@…): Yes, libpixman does do some asm, which is the root cause of the issue... must be making some assumptions about how the compiler is going to emit code, and is noted as a source of issues when moving to llvm. Older versions of clang have additional parsing bugs, some of which I ran into in my own code (and to their credit, the clang team was responsive to my bug reports and I moved pretty easily to svn checkout of clang to use their fixes.) So, really MacPorts should do a version test on the compiler to make the selection: users could have retained an old Xcode 3 install through a Lion upgrade, or inversely, be on Snow Leopard but updated the clang install like I did. So it would be more robust to base the selection on the available clang version instead of the OS version. For reference: * a semi-recent manual build from llvm/clang svn reports --version "clang version 3.0 (trunk 129294)" * the Xcode 4.1 version reports as "Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)" * Xcode 4.0 was "based on LLVM 2.9svn" I'd suggest requiring clang>=3.0 in order to be robust. But more practically, don't worry about it and just fall back to gcc-4.2 for everyone for now :) -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Comment(by ejtttje@…): I think we all agree that llvm-gcc-4.2 is failing. The trick is that although Xcode 4.1's clang works, according to eborisch's log, ''clang fails on this port in Snow Leopard'' (could be Xcode 4.0 or 3... doesn't really matter). So then the only global fallback is gcc-4.2 (note '''non'''-llvm), unless someone wants to test for the actual clang version (and even then, what version works? Xcode 4.0? Current MacPorts? Some random svn revision in-between?) -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Comment(by jmr@…): Although it wouldn't be using llvm-gcc-4.2 in the first place unless he was using Xcode 4, so I guess 4.0.x is also affected. -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Comment(by jeremyhu@…): I'm not saying we should use clang globally. I'm suggesting that we use clang if llvm-gcc-4.2 is the default compiler (ie: if we're on XCode 4.0.x). I suspect the issues with clang are stemming from XCode 3.2.6, but that version of XCode will be using gcc-4.2 anyways and won't be forced to use clang. Once they update to XCode4, they'll have a clang that will work, and pixman will be using it. I'm highly suspicious of eborisch's build log, especially since it's using ccache. It looks like it's not doing something "normal". -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:14> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Comment(by jeremyhu@…): Please report this as well: {{{ xcodebuild -version clang --version }}} -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:16> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Comment(by eborisch@…): Still fails without ccache. Please let me know if there is anything else suspicious I can address. MacPro:~$ xcodebuild -version Xcode 4.0.2 Build version 4A2002a MacPro:~$ clang --version Apple clang version 2.0 (tags/Apple/clang-139) (based on LLVM 2.9svn) Target: x86_64-apple-darwin10 Thread model: posix Logs will be attached. -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:18> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30370: libpixman erroneous execution with llvm-gcc-4.2 --------------------------------+------------------------------------------- Reporter: ejtttje@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Resolution: fixed | Keywords: lion llvm-gcc-4.2 cairo pdf Port: libpixman | --------------------------------+------------------------------------------- Changes (by jmr@…): * status: reopened => closed * resolution: => fixed Comment: r81520, maintainer timeout -- Ticket URL: <https://trac.macports.org/ticket/30370#comment:23> MacPorts <http://www.macports.org/> Ports system for Mac OS