Displaying 6 results from an estimated 6 matches for "universal_arch".
2009 Aug 31
0
[LLVMdev] problems with the 2.6 branch under x86_64
...ally
targeting x86_64 and not i386, but it seems to be the case (though I
may be mistaken).
I suspect the problem might be related to the way I build LLVM. I am
on Mac OS X and need a 2-way fat Intel Universal binary, so I build it
like the following:
$ ./configure
$ UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" ENABLE_OPTIMIZED=1 make
$ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64"
ENABLE_OPTIMIZED=1 make install
Any help will be greatly appreciated :)
Laurent
2007 Sep 20
1
[LLVMdev] Valgrind Help Needed
On Sep 19, 2007, at 5:41 PM, Devang Patel wrote:
> On Sep 19, 2007, at 4:48 PM, Bill Wendling wrote:
>
> In llvm-backend.cpp :
>
> 1086 if (GV->getName() != Name) {
> 1087 Function *F = TheModule->getFunction(Name);
> 1088 assert(F && F->isDeclaration() && "A function turned
> into a global?");
> 1089
2009 Dec 22
1
[LLVMdev] [PATCH] Cross-compiling LLVM on Mac OS X
>> Daniel's comments are also good.
>
> …success!
Looks like I spoke a bit too soon. Everything works as far as the fat binaries are concerned, except that -mmacosx-version-min is set to the host’s OS version, not that of the SDK, causing errors when it tries to link against 10.6’s versions of libraries instead of 10.5’s.
This patch appears to solve that; it uses the OS version
2009 Dec 22
0
[LLVMdev] Cross-compiling LLVM on Mac OS X
...t; Let the build go and see where you get. Also, you need more than a single -arch flag. As I said before -arch ppc -arch i386 -arch x86_64.
This results in x86_64 binaries only, unfortunately. However…
> Daniel's comments are also good.
…success!
> export UNIVERSAL=true
> export UNIVERSAL_ARCH="i386 x86_64 ppc ppc64"
> export UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.5.sdk/
> export CFLAGS="-mmacosx-version-min=10.5"
> export CXXFLAGS="-mmacosx-version-min=10.5"
>
> ./configure --enable-optimized --enable-jit --enable-targets=x86,x86_64,po...
2009 Dec 22
1
[LLVMdev] Cross-compiling LLVM on Mac OS X
On Dec 21, 2009, at 3:39 PM, Rob Rix wrote:
>> Anyhow, Rob, best bet is to just use -arch to build everything up. lipo knows what needs to happen.
>
> Unfortunately that doesn’t appear to be enough; using -arch in CFLAGS (and CXXFLAGS) and not using --build or --host builds for x86_64 no matter what you specify for the architecture (in my case, the documented i386 and ppc).
>
2009 Dec 21
5
[LLVMdev] Cross-compiling LLVM on Mac OS X
Hello,
I’ve spent the past day or so attempting to get LLVM’s libraries built as a Mac OS X-style universal binary, the first step of which is to get them built for each component architecture (i386, x86_64, ppc, and ppc64).
The first two are straightforward as I am working on an x86_64 Mac (running Mac OS X 10.6, which corresponds to Darwin 10), but building ppc binaries has thus far eluded me.