Sent the below from the wrong address: On May 24, 2010, at 3:31 AM, Ryan Govostes wrote:
> Have you installed Rosetta? It's an optional install on 10.6. Without it, > ./configure won't be able to run the built binary. That said, I never > experienced this while writing the scripts, and I think it will prompt you > when you try to run the binary. > > Can you paste the actual build error from config.log? > > Finally, don't use anything installed with MacPorts, as I went to great > lengths to avoid requiring any external dependencies. If glib isn't > compiling, let's start with that one. > > -- Ryan > > On May 21, 2010, at 8:15 PM, Evan Schoenberg, M.D. wrote: > >> >> On May 20, 2010, at 8:48 PM, Colin Barrett wrote: >> >>> On May 20, 2010, at 6:25 PM, Evan Schoenberg, M.D. wrote: >>> >>>> /Users/evands/adium/Dependencies/source/gettext/./configure >>>> --prefix=/Users/evands/adium/Dependencies/build --disable-java >>>> --disable-static --enable-shared --disable-dependency-tracking >>>> --host=powerpc-apple-darwin10 --build=powerpc-apple-darwin10 >>> >>> That looks wrong to me. Shouldn't you be doing: >>> >>>> --host=i386-apple-darwin10 --target=powerpc-apple-darwin9 >>> >>> (darwin10 doesn't make sense here as there is no PPC version of 10.6). I >>> may be totally wrong, as I'm not sure what that --build option is about. >> >> I'm not sure either, but the same build command skips the "Compiler produces >> executable code" check and works just fine on my MacBook Pro (where >> questionable other issues have driven me to trying this on the Mac Mini). >> >> They are running slightly different build numbers (but the same version) of >> gcc... >> >> Mac Mini: >> => gcc --version >> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5659) >> >> MacBook Pro: >> => gcc --version >> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664) >> >> I'm flummoxed. >> >> -Evan >> >
