#33765: glw: build fails on PowerPC systems --------------------------------+------------------------------------------- Reporter: trog24@… | Owner: css@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: powerpc | Port: glw --------------------------------+------------------------------------------- Changes (by ryandesign@…): * keywords: => powerpc Comment: Ok, I can reproduce the problem on my Leopard G4. The relevant part of the log is: {{{ :info:build /bin/sh ../../bin/mklib -o GLw -linker '/usr/bin/gcc-4.0' -ldflags '-L/opt/local/lib -arch ppc' \ :info:build -major 1 -minor 0 -patch 0 \ :info:build -install ../../lib \ :info:build -id /opt/local/lib/libGLw.1.dylib \ :info:build -L../../lib -lGL -lXm -L/opt/local/lib -lXt -lX11 GLwDrawA.o GLwMDrawA.o :info:build mklib: Making Darwin shared library: libGLw.1.0.dylib :info:build lipo: /var/tmp//ccZUGZAl.out and /var/tmp//ccNivMSJ.out have the same architectures (ppc7400) and can't be in the same fat output file }}} MacPorts requests `-arch ppc` (generic PowerPC architecture), but since OS X and MacPorts no longer run on G3 processors, the arch that the compiler actually builds for is ppc7400 (G4 and up). The mklib command they're using actually analyzes the library with `lipo -info` and gathers up the architectures and tries to use them. So the compile command it ends up constructing contains `-arch ppc -arch ppc7400`. When there are multiple `-arch` flags the compiler compiles each arch separately, then tries to glue them together with `lipo`. But since `-arch ppc` and `-arch ppc7400` mean the same thing now, `lipo` throws an error about trying to combine two same-architecture binaries. It looks like [ticket:33763 updating glw to its latest version] would solve this problem. Or we could patch mklib. -- Ticket URL: <https://trac.macports.org/ticket/33765#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS