similar to: [LLVMdev] Linking to LLVM libs from new project

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

llvm[4]: Compiling PoolAllocate.cpp for Release+Asserts build /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp: In member function ‘virtual bool llvm::PoolAllocate::runOnModule(llvm::Module&)’: /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp:403:16: error: ‘class llvm::Constant’ has no member named

On Fri, Apr 11, 2008 at 9:39 AM, Lane Schwartz <dowobeha at gmail.com> wrote: > Hi, > > I am attempting to set up a new frontend project based on the sample > project (I'm following the instructions at > http://llvm.org/docs/Projects.html). In doing so, I hit a problem with > AutoRegen.sh which I worked around, and hit a problem with configure > that I don't

Dear Nikhil, The lib/PoolAllocate code doesn't compile with LLVM mainline, and you don't need it for SAFECode. You can remove PoolAllocate from the list of directories to compile in poolalloc/lib/Makefile. Also, are you using the code from Peter's Github repository? I think Peter made this change in his code already. Regards, John Criswell On 7/29/15 11:27 AM, Nikhil Reddy

Hi, I am attempting to set up a new frontend project based on the sample project (I'm following the instructions at http://llvm.org/docs/Projects.html). In doing so, I hit a problem with AutoRegen.sh which I worked around, and hit a problem with configure that I don't know how to work around. Below is what happens when I attempt to autoconf and configure the sample project that ships

On Sat, Apr 12, 2008 at 3:52 PM, Criswell, John T <criswell at ad.uiuc.edu> wrote: > Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. OK. Here are the complete steps required to successfully build the

Try using the --with-llvmsrc and --with-llvmobj options to explicitly set the locations of your LLVM source tree and object tree, respectively. I faintly recall seeing this error and seem to recall using these options to work around it. -- John T. ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf Of Lane Schwartz [dowobeha at

I’ve run into a bizarre error in which LLVM_SRC/Makefile.rules is trying to access a file that doesn’t exist, even though I’ve made sure to correctly reference the needed file. In LLVM_SRC/Makefile.rules, lines 183 and 184 reference the variable ConfigStatusScript, which is defined as $(PROJ_OBJ_ROOT)/config.status. Given the way PROJ_OBJ_ROOT is defined, this means ConfigStatusScript is defined

Hi John, That worked for me. I am using llvm 3.2 only and following http://safecode.cs.illinois.edu/docs/Install.html So for I am able to make inside llvm/projects/poolalloc by doing such cosmetic changes. Now, when I tried to make inside llvm/projects/safecode, I see another error. kpawar at KPAWAR-LT ~/SAFECode/LLVM_SRC/llvm/projects/safecode $ /usr/bin/clang -cc1 -triple

Hello All, I am getting following error on Ubuntu. My gcc is gcc version 4.4.5. Please let me know if you have any comments/suggestions. In file included from /home/janarbek/Work/llvm/llvm/lib/Support/Path.cpp:299: /home/janarbek/Work/llvm/llvm/lib/Support/Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, std::string*) const’:

Kostya, I think I've found what looks like a reproducible bug in libFuzzer. The code under test is built with ASan and the first ASan CHECK failure shows fuzzer in the stack trace. (see below) One of the factors that may be unique in my testing is that each iteration can take a very long time to execute (tens or hundreds of seconds). Let me know if you need more info, I think it

Kostya, Here's the git repo: https://bitbucket.org/ebadf/fuzzpy I've only tested it on arm7 and x86_64 linux, I expect there's a good chance it may not work on other OSs. If you can build it successfully ("./build.sh", requires clang and clang++ in your path), then you should run the "testemail" case like so: while true; do ITERS=1000 ./run.sh

Ah, yes -- you need to clone with --recursive. I will try the workaround though. On Dec 3, 2015 1:12 PM, "Kostya Serebryany" <kcc at google.com> wrote: > > > On Wed, Dec 2, 2015 at 7:17 PM, Brian Cain <brian.cain at gmail.com> wrote: > >> Kostya, >> >> Here's the git repo: https://bitbucket.org/ebadf/fuzzpy >> >> I've only

On Mon, Oct 24, 2011 at 4:27 PM, janarbek <canarbekmatay at yahoo.com> wrote: > > Hello All, > > I am getting following error on Ubuntu. My gcc is gcc version 4.4.5. Please let me know if you have any comments/suggestions. > > In file included from /home/janarbek/Work/llvm/llvm/lib/Support/Path.cpp:299: > /home/janarbek/Work/llvm/llvm/lib/Support/Unix/Path.inc: In member

Hi Nicolas, I finally found the root of the problem. Build was unable to locate llvm-build because it was looking for it in path/to/vmkit_src/utils/llvm-build while it was located in path/to/llvm_src/utils/llvm-build Actually llvm-build's path is defined by the path/to/llvm_src/Makefile.rules and looks like this LLVMBuildTool := $(PROJ_SRC_ROOT)/utils/llvm-build/llvm-build however in

This document http://llvm.org/docs/Projects.html says the USEDLIBS should be used to statically link libraries: USEDLIBSThis variable holds a space separated list of libraries that should be linked into the program. These libraries must be libraries that come from your *lib* directory. The libraries must be specified without their "lib" prefix. For example, to link libsample.a, you

Hi all, I spent several hours today trying to compile llvm-gcc4 from svn and llvm from cvs on amd64 linux. In the case anyone else decides to try the same, this could ease your pain: 1) check out llvm, llvm-gcc 2) create llvm-obj llvm-gcc-obj export LLVM_INSTAL=<install_dir> cd llvm-obj export LLVM_OBJ=`pwd` ../llvm/configure --prefix=$LLVM_INSTALL --enable-debug-runtime 4) At one point,

Hello, git bisect helped me today in tracking down a regression in LLVM/Clang. Because LLVM/Clang code is split across multiple git repositories, there were a few obstacles to overcome prior to using git bisect. I thought I would share them here, in the hope that they're useful for others. The main difficulty was to check out the version of clang and compiler-rt that would compile with a

Hi, On Linux I observed [root at localhost poolalloc]# find . -name *.a ./Release+Asserts/lib/LLVMDataStructure.a ./Release+Asserts/lib/poolalloc.a ./Release+Asserts/lib/AssistDS.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Asserts/lib/libpoolalloc_rt.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libcount.a On cygwin I observed kpawar at KPAWAR-LT

Hi, I have a debug build with shared libraries (to reduce compilation time), but since yesterday, it's failing with an ExecutionEngine error: FAILED: : && /usr/lib/ccache/bin/c++ -fPIC -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wno-comment -std=c++11