similar to: [LLVMdev] Makefile.config

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

yue wrote: > hi, > about [LLVMdev] another question > > thanks > > yueqiang One other thing you might want to try is to put your object tree in a directory that is *not* inside of your source tree. Currently, we don't support using separate object trees that are subdirectories of the source tree. In other words: Will work: ========== SRC_ROOT=/home/yue/llvm

My final foray into the makefiles for a while has been completed. The dist-check target is the golden nugget I was hoping to get out of automake. But, now LLVM Makefiles have it too. dist-check does the following: * builds everything with "check" to ensure the source of the distribution is sane, essentially "make check". * builds the distribution tar balls with

Hi, In buildling XPS using LLVM's makefile system, I'm finding that there's a few things lacking in our support for LLVM-based projects. The items below should help but may require changes to project makefiles. I thought I'd check before just going and doing it. 1. Various autoconf generated variables (e.g. abs_top_srcdir) are set in the makefiles but not used. They

The proposed makefile changes have been committed. If you are working from CVS head and you use the LLVM Makefile System in your own project, please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements

Hi all, I'm having problems compiling LLVM 3.2 with RTTI enabled. Since my code makes heavy use of the Boost libraries, RTTI is a must. This is the script I use to compile (as root): SRC_ROOT=$PWD OBJ_ROOT=/export/apps/llvm INSTALL_ROOT=/usr/local mkdir -p $OBJ_ROOT cd $OBJ_ROOT $SRC_ROOT/configure --prefix=$INSTALL_ROOT \

Ok, I am trying to configure llvm to compile benchmarks as suggested by John, and after running configure, I get the following error while running make in the /test/Programs/External/SPEC ---- make[1]: Entering directory `/home/llvm/llvm/test/Programs/External/SPEC/CINT95' make[2]: Entering directory `/home/llvm/llvm/test/Programs/External/SPEC/CINT95/099.go'

The proposed makefile changes have been committed. If you are working from CVS head and you use the LLVM Makefile System in your own project, please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements for projects.

Vinay S. Belgaumkar wrote: > Ok, I am trying to configure llvm to compile benchmarks as suggested by > John, and after running configure, I get the following error while > running make in the /test/Programs/External/SPEC Hmmm. It sounds like the Makefiles are not creating the gccld command line correctly. Some questions: 1) Can you send us your Makefile.config? 2) Can you tell us

Does anyone know the "standard" commandline to compile and run spec95 benchmarks ? I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not sure if they are the *default ref* configurations. <Some of them seem to use smaller problem sizes.> SPEC95 was retired many years ago, so few people around me know how to compile and run them. I am building from

The llvm.cs.uiuc.edu site does not seem to be updating at the moment so it contains the old instructions. If you're looking for the new instructions on the Projects.html page, you can view them here: http://illuvium.net/docs/Projects.html Reid. On Sat, 2005-01-15 at 18:30, Reid Spencer wrote: > The proposed makefile changes have been committed. If you are working > from CVS head and

I found use old BUILD_OBJ_ROOT/BUILD_SRC_ROOT in comment in llvm/Makefile.common and in llvm/projects/Stacker/test/Makefile code. I update it to PROJ_* in attached patches. Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile.common.patch Type: application/octet-stream Size: 1081 bytes Desc: not available URL:

Some of the run commandlines don't seem to be the *default ref* configuration. For instance, in 099.go, what's in the script is: LEVEL = ../../../.. BM=099.go ifeq ($(RUN_TYPE),test) STDIN_FILENAME = /dev/null STDOUT_FILENAME = null.out RUN_OPTIONS = 40 19 else STDIN_FILENAME = 2stone9.in STDOUT_FILENAME = 2stone9.out RUN_OPTIONS = 50 9 endif include ../../Makefile.spec95

On Thu, 21 Jul 2005, Long Fei wrote: > Does anyone know the "standard" commandline to compile and run spec95 > benchmarks ? > > I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not > sure if they are the *default ref* configurations. <Some of them seem to use > smaller problem sizes.> SPEC95 was retired many years ago, so few people

On Thu, 21 Jul 2005, Long Fei wrote: > which suggests the compiling command: > gcc -DSPEC_CPU95 -O2 -o spec_go g2.c g22.c g23.c g25.c g26.c g27a.c g27b.c > g28.c g29.c g2eye.c g2jlib2.c g2jos.c g2list.c g2reas.c g2s2.c g2s3.c g2shp.c > and the running commandline: > ./spec_go 50 9 2stone9.in > < are these correct ? > I believe that we only include test/train inputs for

Hi Chris, It did compile when I gave that option. But it gives me an error when I try to run the executable on an Intel machine. ----- 1513158 is not prime. Exception handler needed, but not enabled. Recompile program with -enable-correct-eh-support. lli[0x8429bb4] lli[0x8429dc0] /lib/libc.so.6[0x40128c18] /lib/libc.so.6(abort+0x161)[0x40129cb5] [0x403da922] ../../../i386: line 4: 27606

Hello, I've closed PR106 (use automake) as WONTFIX. I've already delineated the problems with automake in previous posts but as of now, all the automake related stuff has been removed from the repository. In an effort to start making our makefile system better, I've committed changes to Makefile.rules and a few library Makefiles that nearly double the speed of our compilations. I

hi, when i change the OBJ_ROOT and recompile the llvm, it's successful. but run following test, then the error occues: ----------------------------------------------------- [yue at RH9 obj]$ make -C ./test/Programs make: Entering directory `/home/yue/llvm/obj/test/Programs' make[1]: Entering directory `/home/yue/llvm/obj/test/Programs/SingleSource' make[2]: Entering directory

Hello, Bob > download the latest from the head of the trunk, then ran 'configure' under > msys and received the following....  has anyone done this under msys on a > windows pc?? Msys works fine for me. What is the version of msys you're using? What is the version of bash? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

Hi Reid, just a quick note while you're doing this, a while ago I ran into a problem that the standard makefiles weren't building libraries (like, say, a new pass) correctly on OS X - they were being built as shared libraries and not bundles, so they couldn't be loaded with dlopen. The discussion is in the archives if you want more details... I fixed it locally by doing the following