So, yeah, we're supposed to be working on 1.4. It's bothering me that we have a 
broken libpurple build on adium, though.

It seems that glib is the source of the breakage... which is odd, since it 
hasn't changed; breakage dates to my last libpurple framework commit.

I decided maybe it was my machine's fault.  I took my Mac Mini, which had a 
fresh 10.6 install, and installed XCode on it. Checked out adium, and tried to 
run the dependency build scripts on this virginal machine.

1) I couldn't get glib to compile, because it couldn't find libintl.  This, 
despite libintl seeming to build as part of the gettext process and 
subsequently showing up in build/lib.

So after much messing with it,  I just installed gettext to the system via 
macports.

Leading to...

2) Now, glib does admit that libintl exists, and tries to link against our 
freshly built library (in build/lib).  However... it can't, because:

[evands:Gazebo] [19:52:33] [Thu May 20] [~/adium/Dependencies] 
=> file build/lib/libintl.dylib 
build/lib/libintl.dylib: Mach-O dynamically linked shared library i386

gettext isn't building universally. Hm?

When the gettext build process (in xcompile()) gets to configuring the ppc 
architecture, it errors out:

Running command:
        /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
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ../build-aux/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for powerpc-apple-darwin10-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... no

configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
configure: error: ./configure failed for autoconf-lib-link

Any thoughts, o brilliant minds?  I'm not sure how this is working elsewhere... 
does some magic need to be done before cross-compiling is possible?

-Evan

Reply via email to