search for: build_gcc

Thanks for the hint, Devang. On Jul 6, 2007, at 7:26 PM, Devang Patel wrote: > You need to build darwin driver to use -arch. Try using build_gcc > script to configure and build llvm-gcc. Well, I guess this task exceeds my expertise. I just thought there was some obvious mistake I made because a lot of people might be using llvm-gcc4 as a drop-in to Apple's gcc to build multi- architecture binaries. I'll have a look at buil...

On Wed, 11 Jul 2007, Leo Fink wrote: >> You need to build darwin driver to use -arch. Try using build_gcc >> script to configure and build llvm-gcc. > > Well, I guess this task exceeds my expertise. I just thought there > was some obvious mistake I made because a lot of people might be > using llvm-gcc4 as a drop-in to Apple's gcc to build multi- > architecture binaries. Leo,...

On Jul 10, 2007, at 10:41 PM, Chris Lattner wrote: > On Wed, 11 Jul 2007, Leo Fink wrote: >>> You need to build darwin driver to use -arch. Try using build_gcc >>> script to configure and build llvm-gcc. >> >> Well, I guess this task exceeds my expertise. I just thought there >> was some obvious mistake I made because a lot of people might be >> using llvm-gcc4 as a drop-in to Apple's gcc to build multi- >> archi...

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

...hould have their own build script which passes "make" > whichever file > they want to use as the makefile, so then it doesn't need a special > name > like GNUmakefile. Actually, doesn't Apple use a build script already? > We use GNUmakefile to trigger using the build_gcc script. It's not ideal, but it's all we have at the moment. For LLVM, we placed those files in a subdirectory. This isn't ideal because of our build processes, but was better than the alternative. We would *really* prefer not doing the same thing to LLVM-GCC. Because we've b...

Sorry if this has been answered before -- a quick search didn't dig up an answer for me. I'd like to use the llvm-gg4 front-end for cross-compilation (ppc/x86 and vice versa) on Mac OS X. I built it (e.g. on ppc) from source with a configure like this: configure --with-gxx-include-dir=/usr/include/c++/4.0.0 -- build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --

On Jul 6, 2007, at 8:04 AM, Leo Fink wrote: > Built like this, llvm-gcc generates ppc code regardless of the -arch > flag (e.g. arch i386). > > What can I do to make it behave like Apple's gcc in this matter? You need to build darwin driver to use -arch. Try using build_gcc script to configure and build llvm-gcc. - Devang

Hi Bill, > We use GNUmakefile to trigger using the build_gcc script. thanks for the explanation, but I still don't understand why it is done this way. Why not just get Apple people to run some script, rather than trying to have "make" automagically do an Apple build? > It's not > ideal, but it's all we have at the moment. For...

Filed a bug with Apple 10073924  but I'm wondering if anyone else knows what to fix here: Summary: Building a Darwin cross compiler so I can use distcc with my Mac. Host: x86_64-gnu-linux with GCC 4.5.3. Steps to Reproduce: Download tar ball tar xvf llvmgcc42-2335.15.tar.gz mkdir gcc-build cd gcc-build CFLAGS="-w -m32" CXXFLAGS="$CFLAGS" CPPFLAGS="$CFLAGS"

On Tue, Apr 7, 2009 at 12:38 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Bill, > >> We use GNUmakefile to trigger using the build_gcc script. > > thanks for the explanation, but I still don't understand why > it is done this way.  Why not just get Apple people to run some > script, rather than trying to have "make" automagically do an > Apple build? > It's more complicated than that. Suffice it...

...lcc_dynamic is not required and the configure.ac test above is redundant. AFAIK gcc-4.0 cannot be used with g77. Apple have been adding 'APPLE LOCAL' mods to gfortran and it can now be built from current Apple sources simply by adding f95 to the -- enable-languages on line 102 of the build_gcc script. I suspect that in the not too distant future gfortran will become part of the Xcode packages. Bill Northcott

On Saturday 04 April 2009 19:12:55 Mike Stump wrote: > On Apr 4, 2009, at 6:17 AM, Duncan Sands wrote: > > you need to use a separate objects directory and not build directly > > in the llvm-gcc tree. For some reason the Apple people placed a file > > GNUmakefile in the tree which "make" chooses in preference to the > > Makefile > > produced by

On Apr 4, 2009, at 6:17 AM, Duncan Sands wrote: > you need to use a separate objects directory and not build directly > in the llvm-gcc tree. For some reason the Apple people placed a file > GNUmakefile in the tree which "make" chooses in preference to the > Makefile > produced by configuring. Personally I would like to see GNUmakefile > deleted. My take, you can

So my original post subject was for -march, but that was my mistake. The command line option is -arch. Since presumably Macports is just fetching an llvm tar ball from some repository, is the issue that llvm has been misconfigure in some obvious way? Yes, I can take a look at the driverdriver.c source file as well. Should this also be working in LLVM 2.9 or is the latest SVN also needed? On

On Aug 22, 2011, at 3:59 PM, Bob Wilson wrote: > The -arch option is handled by Apple's "driver-driver", and the MacPorts build is probably not using that. See the driverdriver.c source file in llvm-gcc for details. > He's asking about the -march option which should work either way. Also, the driver-driver should be in the sources that they're using even still.