[MacPorts] #24393: mesa-7.8.1 on Tiger PPC: Unsupported platform, No pipe_atomic implementation selected
MacPorts
noreply at macports.org
Sat Apr 17 23:05:48 PDT 2010
#24393: mesa-7.8.1 on Tiger PPC: Unsupported platform, No pipe_atomic
implementation selected
----------------------------------+-----------------------------------------
Reporter: emily@… | Owner: jeremyhu@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.8.2
Keywords: tiger | Port: mesa
----------------------------------+-----------------------------------------
Comment(by ryandesign@…):
Replying to [comment:6 stephen@…]:
> The patch I'm about to upload does permit building, but I have no idea
if it's correct or not.
Your patch uses PIPE_ATOMIC_GCC_INTRINSIC if no other methods were found
to work. But the code was deliberately changed upstream to
[http://cgit.freedesktop.org/mesa/mesa/commit/?id=930838efcdac04dd0a0c7ee0375364548a0efe8c
only use PIPE_ATOMIC_GCC_INTRINSIC if GCC 4.1 or greater is found], and
Leopard and Tiger come with GCC 4.0.1, so I would not be comfortable
second-guessing them on this decision. The commit message does not explain
why this change was made; we could ask the author of the change for more
information.
> I don't understand why this port builds anywhere,
I haven't analyzed the source code in any great detail, but with a little
testing I found that on Tiger Intel, it uses PIPE_ATOMIC_ASM_GCC_X86; on
Snow Leopard (where GCC 4.2.1 is the default), it uses
PIPE_ATOMIC_GCC_INTRINSIC; and on Leopard PPC it also uses
PIPE_ATOMIC_GCC_INTRINSIC, thanks to the change in r65971 that makes the
port use Leopard's Xcode's optional GCC 4.2.1.
One possible solution this information leads us to is using a MacPorts GCC
port (gcc45, gcc44, etc.) for mesa on Tiger PowerPC. That would have
implications for building universal, but not if we use the compiler in the
apple-gcc42 port. And it's a heavy dependency in that the GCC ports take a
long time to build, especially for older slower PowerPCs, which are
exactly the set of Macs affected by the problem. :/
--
Ticket URL: <http://trac.macports.org/ticket/24393#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list