search for: driverdriv

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 Mon, Aug 22, 2011 at 6:03 PM, Eric Christopher <echristo at apple.com> wrote: > > On Aug 22, 2011, at 3:59 PM, Bob Wilson wrote: > >> The -arch option is handled by Apple'...

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. Nichols: You might want to talk to the llvm-gcc port maintainer. There's nothing obviously...

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. On Aug 22, 2011, at 3:08 PM, Nichols A. Romero wrote: > Here is some more info: > > [naromero:~/pmr] naromero% llvm-gcc -v > Using built-in specs. > Target: x86_64-apple-darwin10 > Configured with: ../llvm-gcc-4.2-2.9.source/configure &g...

Here is some more info: [naromero:~/pmr] naromero% llvm-gcc -v Using built-in specs. Target: x86_64-apple-darwin10 Configured with: ../llvm-gcc-4.2-2.9.source/configure --prefix=/opt/local --host=x86_64-apple-darwin10 --enable-llvm=/opt/local --enable-languages=c,c++,objc,obj-c++,fortran --libdir=/opt/local/lib/llvm-gcc42 --includedir=/opt/local/include/llvm-gcc42 --infodir=/opt/local/share/info