On Wed, Feb 25, 2009 at 11:52:49PM -0600, Ryan Schmidt said: > On Feb 25, 2009, at 19:17, Joshua Root wrote: > >> This is the main problem that trace mode (-t) was designed to solve. > > Speaking of trace mode, it doesn't work for me. Fails during extract > already: > > $ port -dt extract zlib [...] > DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4' > DEBUG: Assembled command: 'cd "/mp/var/macports/build/ > _Users_rschmidt_macports_dports_archivers_zlib/work" && /mp/bin/bzip2 -dc > /mp/var/macports/distfiles/zlib/zlib-1.2.3.tar.bz2 | /usr/bin/gnutar > --no-same-owner -xf -' > Warning: setrlimit failed (1) > dyld: could not load inserted library: /mp/share/macports/Tcl/ > darwintrace1.0/darwintrace.dylib > > > The problem seems to be that darwintrace.dylib is compiled for i386 only > but my bzip2 is 4-way universal. If I deactivate bzip2 +universal and > install bzip2 non-universal it extracts fine. > > So for darwintrace to work with 4-way universal ports, I need to build > MacPorts base as 4-way universal? I have tried, but I get: > > > checking objc/objc.h usability... yes > checking objc/objc.h presence... yes > checking for objc/objc.h... yes > checking if linking libobjc requires pthreads... no > checking for Apple Objective-C runtime... no > checking for GNU Objective C runtime... no > configure: error: Could not locate a working Objective-C runtime. > See `config.log' for more details.
Note that /usr/lib/libobjc.A.dylib, on 10.4, is only a 32bit universal library, so perhaps that's what's keeping the 64bit side from working? Bryan _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
