similar to: [LLVMdev] LLVM-GCC builds on OS X 10.5, fails on 10.6

It looks like you're building a 32-bit llvm-gcc and trying to link it against 64-bit llvm libraries. Try specifying the triple as x86_64-apple-darwin10 instead of i686-apple-darwin9. -Jim On Jan 27, 2011, at 7:29 AM, Trevor Harmon wrote: > Hi, > > For months now I've been building LLVM-GCC on a Mac OS X laptop without problems. Recently I switched to a different laptop, and I

On Jan 27, 2011, at 1:42 PM, Jim Grosbach wrote: > It looks like you're building a 32-bit llvm-gcc and trying to link it against 64-bit llvm libraries. Try specifying the triple as x86_64-apple-darwin10 instead of i686-apple-darwin9. Yep, that was it... thanks! It looks like I can generalize the TRIPLE setting to: export TRIPLE=$MACHTYPE and it will pick up either

On Apr 1, 2010, at 4:45 AM, naohk wrote: > Correct me if I'm wrong. To build llvm, you'd need llvm-gcc front-end. The Getting Started Guide is a bit misleading on this point because the "Install the llvm-gcc-4.2 front end" step comes before the "Build the LLVM Suite" step, implying that LLVM GCC is a dependency, but it's not. FWIW, here's how I build

I'm running into the same error. Correct me if I'm wrong. To build llvm, you'd need llvm-gcc front-end. You're saying we'd need llvm in order to build llvm-gcc. So how should we kick start the process? Thanks. Duncan Sands wrote: > > Hi Eliseu, > >> 2. I've unpacked llvm-gcc-4.2-2.6.source.tar.gz under the llvm-gcc >> directory. I've also

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

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:

Still nothing here: [yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64 [yendi:~] echristo% So, perhaps you could send more information? Or bug the mac ports people. -eric On Aug 22, 2011, at 2:44 PM, Nichols A. Romero wrote: > This comes up when trying to compile Valgrind, here is the full compile line: > > /opt/local/bin/llvm-gcc-4.2 -Wbad-function-cast -Wcast-qual

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1660387551-1458482416-1249639718=:2997 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: <Pine.LNX.4.64.0908071039211.2997 at parser.ilovebacon.org> Hello, There appears to be a bug in the nlm function, which I

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.

Hm, I also note that: $ file /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as: Mach-O 64-bit executable x86_64 Why's the i386 package have an x86_64 binary in it? That could explain why it doesn't work on darwin9. On Fri, Mar 19, 2010 at 9:49 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Hi Tanya, > > On darwin9, the

Hi Tanya, On darwin9, the binaries in the darwin10 packages give: $ /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as --help dyld: unknown required load command 0x80000022 Trace/BPT trap That could be unavoidable, of course. Also, could you document what build mode the packages use (or release both Debug and Release-Asserts packages)? Since +Asserts and -Asserts have different ABIs, I'd have

This comes up when trying to compile Valgrind, here is the full compile line: /opt/local/bin/llvm-gcc-4.2 -Wbad-function-cast -Wcast-qual -Wcast-align -fstrict-aliasing \ -arch x86_64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -mmacosx-version-min=10.5 -fno-stack-protector \ -O -S

I'm on OSX 10.5, trying to build a svn checkout of llvm-gcc. I've also checked out llvm. Both are synced to r61075. I'm using Apple's gcc 4.0.1: $ gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /var/tmp/gcc/gcc-5488~2/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++

On Feb 15, 2010, at 1:17 PM, David Greene wrote: > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: >> On Feb 15, 2010, at 1:04 PM, David Greene wrote: >>>> FWIW, this is because you broke the encoding of an instruction in your >>>> patch. This is incorrect: >>>> >>>> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins

Hi, I'm wanting to call R from Perl via the RSPerl package. However I cannot seem to install it on my Macbook (OS X Tiger - R 2.6 - Perl 5.8.6). I try to install the source downloaded from the sigmahat website - but it seems to fail - when I search my system for R.pm - I can't find it? Something looks to be going wrong with the make bits? Cheers David M ---- $ R CMD INSTALL

The 2.7 binaries are available for testing: http://llvm.org/pre-releases/2.7/pre-release1/ You will also find the source tarballs there as well. We rely on the community to help make our releases great, so please help test 2.7 if you can. Please follow these instructions to test 2.7: To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it

building 'smb' extension x86_64-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -march=nocona -O2 -fomit-frame-pointer -pipe -D_SAMBA_BUILD_=3 -fPIC -I/usr/include/python2.5 -c python/py_smb.c -o build/temp.linux-x86_64-2.5/python/py_smb.o -march=nocona -O2 -fomit-frame-pointer -pipe -D_SAMBA_BUILD_=3 -DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -march=nocona

Has anyone successfully compiled pnmath (http://www.stat.uiowa.edu/~luke/R/experimental ) for an intel processor running mac OS 10.5? When I attempt to do so via the R package installer (choosing "Local Source Package" and pointing to the pnmath_0.0-2.tar.gz file), I get the following errors: * Installing *source* package 'pnmath' ... ** libs ** arch - i386 gcc -arch i386

I try to install Rmpi as root with install.packages("Rmpi"). It fails with: ... checking for x86_64-pc-linux-gnu-gcc -std=gnu99 option to accept ISO C89... none needed I am here /usr and it is OpenMPI Trying to find mpi.h ... Found in /usr/include Trying to find libmpi.so or libmpich.a ... Found libmpi in /usr/lib checking for openpty in -lutil... yes checking for main in -lpthread...

Can anyone shed some light on the origins of the comments... /* Mach-O doesn't support omitting the frame pointer for now. */ ...in gcc/config/i386/i386.c. FSF gcc trunk has enabled the omit-frame-pointer option as the default for both i386 and x86_64 recently. * config.gcc: Handle --enable-frame-pointer. * configure.ac: Add --enable-frame-pointer. * configure: Regenerated. *