search for: build_typ

Greetings all, In looking at the API for ActiveRecord::Associations::ClassMethods there doesn''t appear to be a way to rename an association. In doing some refactoring I am replacing one table with two but want to preserve the old associations names, e.g. I want to be able to still say build_type.artifacts instead of having to use the new table name: build_type.build_type_artifacts. Is an alias my only option or am I missing something glaringly obvious? John-Mason Shackelford Software Developer Pearson Educational Measurement 2510 North Dodge St. Iowa City, IA 52245 ph. 319-354-9200x...

...Configure LLVM to build with a cross-compiler. To do this, supply the configure script with --build and --host options that are different. The values of these options must be legal target triples that your GCC compiler supports. 4. Put the saved TableGen executable into the into $LLVM_OBJ_ROOT/{BUILD_TYPE}/bin directory (e.g. into .../Release/bin for a Release build). 5. Build LLVM as usual. ... but all this messing about with tblgen seems to be completely unnecessary now, presumably since this commit: http://llvm.org/viewvc/llvm-project?view=rev&revision=58981 Thanks, Jay.

...Nov 07, 2004 at 11:40:58PM +0100, Basile STARYNKEVITCH wrote: > I did "make" inside llvm/examples/ and inside > llvm/examples/HowToUseJIT/ and expected to get an ELF executable.. But > I've only got the 2 Release/HowToUseJIT.[do] files.. All executables are placed in tools/$(BUILD_TYPE), in your case, llvm/tools/Release. That is there from the time before we had the examples/ directory, and the only executables produced were the tools. Perhaps that should be changed to build into examples/$(BUILD_TYPE) ... > > Bottom line: you don't need llvm/runtime. > > Wh...

Le Sun, Nov 07, 2004 at 04:14:19PM -0600, Misha Brukman écrivait/wrote: > On Sun, Nov 07, 2004 at 11:04:58PM +0100, Basile STARYNKEVITCH wrote: Basile>> First, I am extremely confused by the terminology. IMHO, the runtime Basile>> libraries would include (from my JIT only perspective) Basile>> 1. all the LLVM libraries required to JIT-generate machine code, and

And it runs linux. http://www.zip4x4.com/ZIP4x4.htm Anyone seen one? bkw

...unix /usr/ccs/bin/ld -dy -b -o obj64/unix -e dboot_image -znointerp -M ../../i86pc/conf/Mapfile.amd64 \ ./obj64/unix.o obj64/dboot.o ./obj64/modstubs.o -L ../../intel/genunix/obj64 -l genunix \ obj64/libdtracestubs.so *** Error code 1 *** Error code 1 The following command caused the error: BUILD_TYPE=OBJ64 VERSION=''onnv-bugfixes'' make all.targ *** Error code 1 The following command caused the error: cd unix; pwd; make all *** Error code 1 The following command caused the error: cd i86pc; pwd; make all *** Error code 1 The following command caused the error: cd uts; pwd; ma...

I'm trying to cross-compile LLVM with build=, host=target=. I'm using the following packages from Debian lenny: mingw32 4.2.1.dfsg-1 mingw32-binutils 2.18.50-20080109-1 mingw32-runtime 3.13-1 The first problem I hit was when I configured with CC, CXX, AR and RANLIB set to mingw cross-tools, but forgot to specify NM as well. This resulted in a load of warnings that scrolled off the