similar to: [LLVMdev] ICE while building llvm-gcc

On Dec 16, 2008, at 10:34 AM, Jeffrey Yasskin wrote: > 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. hi Jeffrey, This patch should have fixed the problem: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20081215/071210.html Please update and try again, sorry for the breakage! -Chris

Thanks for the quick answer! Syncing to r61112 got rid of the ICE, but I still get the following error: make "DESTDIR=" "RPATH_ENVVAR=DYLD_LIBRARY_PATH" "TARGET_SUBDIR=i686-apple-darwin9" "bindir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/bin" "datadir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/share"

On OS X 10.5.5 I get an error that ld doesn't support -export-dynamic: dhcp-172-19-103-185:~/src/llvm/trunk_nolibtool/obj jyasskin$ ../src/configure --prefix=`pwd`/../install && make VERBOSE=1 ... dhcp-172-19-103-185:~/src/llvm/trunk_nolibtool/obj jyasskin$ make VERBOSE=1 for dir in lib/System lib/Support utils lib/VMCore lib tools/llvm-config tools docs; do \ if [ ! -f

I'm trying to build the 2.5 prerelease on my MacBook, and I'm getting a bus error in tblgen: $ rm -r * && ../src/configure --prefix=`pwd`/../install && make -j1 VERBOSE=1 ENABLE_OPTIMIZED=0 ... llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td /Users/jyasskin/src/llvm-2.5/obj/Debug/bin/tblgen -I /Users/jyasskin/src/llvm-2.5/src/lib/VMCore -I

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 Bill, this might be a latent bug related to PPC. I have no such machine to access atm., but I shall be able to reproduce the problem when back at home. (In about 4 hours). I keep you informed. Cheers, Gabor On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote: > Something last night broke the build on Darwin PPC. Possible Gabor's   > check-in? > > -bw

Something last night broke the build on Darwin PPC. Possible Gabor's check-in? -bw Begin forwarded message: > From: admin at spang.apple.com (admin) > Date: March 4, 2009 3:56:10 AM PST > To: wendling at apple.com > Subject: PPC Nightly Build Result > > /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- > powerpc-powerpc/./prev-gcc/xgcc

For those of you who haven't noticed, I'm planning to commit a major change to the Makefile rules tomorrow evening (Tuesday) if there are no complaints about it between now and then. This needs testing on Darwin. I've heard back from Linux on many platforms and even FreeBSD, which is fantastic, but I'm told that lots of LLVMers are running Darwin and I haven't heard a peep

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

Hello, Pazzo > I had a look to llvm (2.6) configure options but I couldn't find any > way to specify cpu type, fpu ecc.. These are not llvm configure options, but gcc's one. Basically, you should configure llvm-gcc in the same way you do for gcc for your platform. > Could you please give me any > indication and/or example? I want to try llvm with Atmel's > AT91SAM7X256

> > Using built-in specs. > Target: i686-apple-darwin9 > Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ > src/configure --disable-checking --enable-werror --prefix=/Developer/ > usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man -- > enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program- >

Dear Anton, Thanks for your help! I had a look to llvm (2.6) configure options but I couldn't find any way to specify cpu type, fpu ecc..Could you please give me any indication and/or example? I want to try llvm with Atmel's AT91SAM7X256 (core is ARM7TDMI ) Thank you again, pz 2010/1/9 Anton Korobeynikov <anton at korobeynikov.info>: > Hello > >> But I got the

On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote: >> >> Using built-in specs. >> Target: i686-apple-darwin9 >> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ >> src/configure --disable-checking --enable-werror --prefix=/Developer/ >> usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man -- >>

llvm itself is built with gcc-4.0, but the run line is: // RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 | grep {i32 1} | count 2 According the log: FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+ +Frontend/2008-02-13-sret.cpp Failed with exit(1) at line 1 while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /

FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >

Hello, I''m having some issues building r190 on Leopard (10.5.1): $ rake (in /Users/johan/temp/superredcloth) ragel superredcloth_scan.rl | rlgen-cd -G2 -o superredcloth_scan.c ragel superredcloth_inline.rl | rlgen-cd -G2 -o superredcloth_inline.c /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby extconf.rb checking for main() in -lc... yes creating Makefile make gcc -I.

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make

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

I was looking at mod_trace (http://prefetch.net/projects/apache_modtrace/index.html ) and playing with getting it to compile on OS X. When building for x86_64 with -arch x86_64 we get bad instructions generated: gcc -o foo -arch x86_64 foo.c /var/folders/rV/rV1x2DafFr0R6tGG+1bbk++++TM/-Tmp-//ccnykQ1o.s:11:bad register name `%%esi)'' Using gcc -S I can definitely see we are not

The current llvm/llvm-gcc-4.2 svn when built on i686-apple-darwin9 still produces the bogus warnings... f951: warning: command line option "-Wformat" is valid for C/C++/ObjC/ObjC++ but not for Fortran f951: warning: command line option "-Wformat-security" is valid for C/C++/ObjC/ObjC++ but not for Fortran whenc compling any code with gfortran. This causes the gfortran