Problems building libpurple dependencies

[Jeremy Brown]

So, I *was*& working off of the 1.5 branch, but then I realized that 
makes no sense for what I'm trying to do...so I nuked that and checked 
out the 1.3 branch  instead (current release, right?) and I'm still 
running into the same basic problem:

=======
configure:30198: $? = 0
configure:30213: result: yesconfigure:30225: checking if malloc() and 
friends prototypes are gmem.h compatible
configure:30260: /usr/bin/gcc-4.0 -c 
-L/Users/jeremy/src/adium-1.3/Utilities/dep-build-scripts/build/root-ppc/lib 
-I/Users/jeremy/src/adium-1.3/Utilities/dep-bu
ild-scripts/build/root-ppc/include -lintl -liconv 
-mmacosx-version-min=10.4 -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-arch ppc -Wall -Werror -L/Users/jeremy/src/adium-1.3/
Utilities/dep-build-scripts/build/root-ppc/lib 
-I/Users/jeremy/src/adium-1.3/Utilities/dep-build-scripts/build/root-ppc/include 
-lintl -liconv -mmacosx-version-min=10.4 -is
ysroot /Developer/SDKs/MacOSX10.4u.sdk -arch ppc conftest.c >&5
powerpc-apple-darwin10-gcc-4.0.1: -lintl: linker input file unused 
because linking not
 done
powerpc-apple-darwin10-gcc-4.0.1: -liconv: linker input file unused 
because linking no
t done
powerpc-apple-darwin10-gcc-4.0.1: -lintl: linker input file unused 
because linking not
 done
powerpc-apple-darwin10-gcc-4.0.1: -liconv: linker input file unused 
because linking no
t done
configure:30266: $? = 0
configure:30286: result: yes
configure:30290: checking for growing stack pointer
configure:30298: error: cannot run test program while cross compiling
See `config.log' for more details.
=====

A couple of things worth noting that I did different this time: I 
installed the 10.4 SDK since it sounded like 1.3 required it, and I also 
forced use of GCC 4.0.  I also did "sudo port install automake" and 
ended up with automake 1.11.

I keep feeling like there must be something weird with my machine 
configuration that must be causing this.  Is there something obvious I'm 
missing?  Does Adium just not build on SL?

Jeremy

Stephen Holt wrote:
> Those build scripts are for 1.4 and earlier.  If you're working off 
> the adium-1.4 branch, there's a problem.
>
> If you're working on the 1.5 repository, however, there's a new build 
> script in "Dependencies/"  that we're using to build the 32/64 libpurple.
>
>
> ...we should probably document that somewhere.
>
> On Fri, Oct 23, 2009 at 10:50 PM, Jeremy Brown <jeremy at brownjava.org 
> <mailto:jeremy at brownjava.org>> wrote:
>
>     Hi adium-devel!
>
>     About a week ago I commented on this bug that someone else had filed:
>
>     http://trac.adium.im/ticket/13144
>
>     As of the latest Adium it still appears not to be working.  So I
>     decided I would try to obtain a fresh copy of libpurple and
>     rebuild it myself, using the instructions at
>     "Utilities/dep-build-scripts/README".
>
>     Everything works peachy until I run
>     "general_dependencies_make.sh".  It fails silently to build glib.
>      The following lines at the end of "build/dep_make.log" appear to
>     show a problem running glib's configure script...something about
>     being unable to cross compile a test program:
>
>     =============================================
>     checking size of char... 1
>     checking size of short... 2
>     checking size of long... 4
>     checking size of int... 4
>     checking size of void *... 4
>     checking size of long long... 8
>     checking size of __int64... 0
>     checking for format to printf and scanf a guint64... none
>     checking for an ANSI C-conforming const... yes
>     checking if malloc() and friends prototypes are gmem.h
>     compatible... yes
>     checking for growing stack pointer... configure: error: cannot run
>     test program while cross compiling
>     See `config.log' for more details.
>     =============================================
>
>     Sorry to bug the list but I wondered if anyone's run into
>     something like this, or if there's anything obvious I'm missing.
>      I'm running 10.6.1 on an Intel MacBook Pro 17", and I'm using
>     Xcode 3.2 (1610).  GCC version is i686-apple-darwin10-gcc-4.2.1.
>
>     Any ideas?
>
>     Jeremy
>
>
>