[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freetds
Subject:    Re: [freetds] Configure Freetds on 64bit Xserve Failed.
From:       Daniel Fazekas <fdsubs () t-online ! hu>
Date:       2008-04-05 3:09:22
Message-ID: 6F032EE6-DF99-4A10-86D2-D1B00E7594C6 () t-online ! hu
[Download RAW message or body]

On Apr 5, 2008, at 01:11, Tony Wang wrote:

> I did it like this:
> $ cd freetds-0.64
> $ ACOSX_DEPLOYMENT_TARGET=10.5 CFLAGS="-arch ppc -arch ppc64 -arch
> i386 -arch x86_64 -g -Os -no-cpp-precomp" CCFLAGS="-arch ppc -arch
> ppc64 -arch i386 -arch x86_64 -g -O -pipe" CXXFLAGS="-arch ppc -arch
> ppc64 -arch i386 -arch x86_64 -g -Os -pipe" LDFLAGS="-arch ppc -arch
> ppc64 -arch i386 -arch x86_64 -bind_at_load" ./configure --enable- 
> shared
[...]
> gcc-4.0: -E, -S, -save-temps and -M options are not allowed with
> multiple -arch flags

That's a scary thing to do, trying to build an Autoconf-based project  
for multiple CPU architectures simultaneously, trying to create a  
Universal binary in one go.

You should only keep -arch x86_64 and remove all the others.
Then, if you really need a Universal binary, build for the other  
architectures separately too, and use the lipo tool to bundle them  
together into Universal binaries.

But on an Intel-based Xserve running Leopard, x86_64 should be all you  
need.

--
fds
_______________________________________________
FreeTDS mailing list
FreeTDS@lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds
[prev in list] [next in list] [prev in thread] [next in thread]