search for: llvmtooldir

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

...m for cygwin in future) - I have not checked llvmc. * TODO - check system's stdc++.dll and use it with autoconf. -------------- next part -------------- diff --git a/Makefile.rules b/Makefile.rules index 66666b4..2a2128b 100644 --- a/Makefile.rules +++ b/Makefile.rules @@ -498,6 +498,25 @@ LLVMToolDir := $(LLVM_OBJ_ROOT)/$(BuildMode)/bin LLVMExmplDir:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +Share...

> Vladimir, > > I took a *very quick* look at your patch. I won't be able to look at it in > more detail until this weekend, but perhaps you can address a couple of > concerns: > > 1. I don't understand the need for LLVMToolDirSlash. This seems like a > gratuitous change to me. If LLVM_OBJ_ROOT (with LLVM_SRC_ROOT) and LLVM_ROOT both not set without LLVMToolDirSlash we will have "/gccas$(EXEEXT)", for example. This is not problem for project that not use LLVM tools and libs. But this not permite one useful...

Vladimir, I took a *very quick* look at your patch. I won't be able to look at it in more detail until this weekend, but perhaps you can address a couple of concerns: 1. I don't understand the need for LLVMToolDirSlash. This seems like a gratuitous change to me. 2. I don't think the change to CPP.Flags is right. It won't find the LLVM header files 3. Removing the .PRECIOUS line will interfere with correct operation of parallel (make -j N) builds. 4. I don't understand why LLVMUsedLibs...

>> Patch attached. >> >> This patch with header installation patch ( >> http://mail.cs.uiuc.edu/pipermail/llvmdev/2005-February/003300.html ) >> let external project (I am test it at my YAFL frontend for LLVM) build >> using installed LLVM version instead using LLVM obj/src dirs. > > I think the patch looks basically sane. The one wierd thing I notice

On Thu, 2007-07-19 at 21:03 -0700, Chris Lattner wrote: > On Thu, 19 Jul 2007, Reid Spencer wrote: > > With the pending reorganization of the software, I have some questions > > about how developers set their PATH and LD_LIBRARY_PATH variables when > > working with LLVM. This is a bit long winded, but bear with me. > > ok :) > > > We're planning to break

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

...; With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University > -------------- next part -------------- diff --git a/Makefile.rules b/Makefile.rules index 66666b4..8b50eb6 100644 --- a/Makefile.rules +++ b/Makefile.rules @@ -498,6 +498,26 @@ LLVMToolDir := $(LLVM_OBJ_ROOT)/$(BuildMode)/bin LLVMExmplDir:= $(LLVM_OBJ_ROOT)/$(BuildMode)/examples #-------------------------------------------------------------------- +# Locations of shared libraries +#-------------------------------------------------------------------- + +SharedPrefix := lib +Sh...

...abhi232/Desktop/LLVM/llvm-1.9/Release/bin/gccas', needed by `/net/hc287/abhi232/Desktop/LLVM/llvm-1.9/runtime/libprofile/Release/BasicBlockTracing.bc'. Stop. So I looked into the Makefile.common and then in Makefile.rules. Inside Makefile.rules I found that the ifndef GCCAS GCCAS := $(LLVMToolDir)/gccas$(EXEEXT) endif And somehow this is not set is what I am guessing. Is there some option that I need to specify when I am doing gmake in the source folder? Please some advice on this issue. -- Abhinav Karhu MS Computer Science Georgia Institute of Technology

...--------------------------------------------------------- > OBJDIR := $(BUILD_OBJ_DIR)/$(CONFIGURATION) > LIBDIR := $(BUILD_OBJ_ROOT)/lib/$(CONFIGURATION) > TOOLDIR := $(BUILD_OBJ_ROOT)/tools/$(CONFIGURATION) > LLVMLIBDIR := $(LLVM_OBJ_ROOT)/lib/$(CONFIGURATION) > LLVMTOOLDIR := $(LLVM_OBJ_ROOT)/tools/$(CONFIGURATION) > > -#------------------------------------------------------------------------------ > +#-------------------------------------------------------------------- > # Full Paths To Compiled Tools and Utilities > +#-----------------------------...

On Thu, 3 Feb 2005, Vladimir Merzliakov wrote: >> Doing it this way >> allows you to re-use the LLVM build system, as opposed to building your >> own set of Makefiles. > I have pre-LLVM projects in C++ with often used at Unix C++ source file > extention .cc > I modify LLVM build system (original LLVM Makefile.rules already partly > support .cc extention, > for

...set project use for build installed LLVM dir or else project can use only LLVM tools in PATHs if installed LLVM dir added to PATH Also i remove LLVMExmplDir (i not found any it uses in llvm, llvm-java, llvm-test CVS modules) And remove redundent line (as i think): .PRECIOUS: $(LLVMLibDir)/.dir $(LLVMToolDir)/.dir $(LLVMExmplDir)/.dir Any comments? Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile.rules.patch Type: application/octet-stream Size: 6145 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050207/706...

> Doing it this way > allows you to re-use the LLVM build system, as opposed to building your > own set of Makefiles. I have pre-LLVM projects in C++ with often used at Unix C++ source file extention .cc I modify LLVM build system (original LLVM Makefile.rules already partly support .cc extention, for example, in Sources and FakeSources make vars setup code). Is attached patch

...\ - -I $(PROJ_SRC_ROOT)/lib/Target +TableGen = $(TBLGEN) -I $(call SYSPATH, $(PROJ_SRC_DIR)) \ + -I $(call SYSPATH, $(PROJ_SRC_ROOT)/include) \ + -I $(call SYSPATH, $(PROJ_SRC_ROOT)/lib/Target) Archive = $(AR) $(AR.Flags) LArchive = $(LLVMToolDir)/llvm-ar rcsf ifdef RANLIB @@ -1248,57 +1249,57 @@ $(TARGET:%=$(ObjDir)/%GenRegisterNames.inc.tmp): \ $(ObjDir)/%GenRegisterNames.inc.tmp : %.td $(ObjDir)/.dir $(Echo) "Building $(<F) register names with tblgen" - $(Verb) $(TableGen) -gen-register-enums -o $@ $< + $(Verb) $...

...FORCE + ifdef TESTSUITE CLEANED_TESTSUITE := $(patsubst %/,%,$(TESTSUITE)) CLEANED_TESTSUITE := $(patsubst test/%,%,$(CLEANED_TESTSUITE)) @@ -49,22 +52,23 @@ endif ifneq ($(RUNTEST),) -check-local:: site.exp +check-local:: $(SITE_EXP) ( ulimit -t 600 ; ulimit -d 512000 ; \ PATH="$(LLVMToolDir):$(LLVM_SRC_ROOT)/test/Scripts:$(PATH)" \ $(RUNTEST) $(RUNTESTFLAGS) ) else -check-local:: site.exp +check-local:: $(SITE_EXP) @echo "*** dejagnu not found. Make sure 'runtest' is in your PATH, then reconfigure LLVM." endif ifdef TESTONE -CLEANED_TESTONE := $(pats...

Hello, I have tried a lot fix this error but am not able to can you please find me a solution am trying to compile the SAFECode in Cygwin Environment to work for windows. used make -j4 command to make the files in cygwin i have got this error make[5]: Leaving directory '/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include' /usr/bin/cp: cannot stat