similar to: [LLVMdev] The configure script seems to strip some / from path

On Sat, 2005-06-18 at 10:32 +0200, Henrik Bach wrote: > Hi LLVMers, > > The root of my SRC_DIR is: /home/hb/projects/src/llvm-1/llvm/ > and the root of my OBJ_DIR is: /home/hb/projects/build/FC1/llvm-1-1. > > However, the configure script seems to have stripped some of the / from the > paths: > Makefile.common:63: /home/hb/projects/buildFC1llvm-1-1/Makefile.config: No

Hi, Now, I've build the tools and the cfe. However, 'make check' gave me the attached results. Summarized as follows: # of expected passes 1081 # of unexpected failures 26 # of expected failures 32 I configured llvm with following options: '--prefix=/home/hb/llvm/ --enable-targets=host-only'. I used gcc version 3.4.2 to build the tools and cfe. The cfe is version:

Hi Henrik, You don't have the latest C/C++ Front End Source code. Please update from CVS to get the fix for the 2005-06-15-ExpandGotoInternalProblem.c test. Note the date of the test (5 days ago). Reid. On Mon, 2005-06-20 at 18:42 +0200, Henrik Bach wrote: > Hi, > > Now, I've build the tools and the cfe. However, 'make check' gave me the > attached results.

Hi Reid, Now, I've removed the file and updated the source tree with this command: cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm update -PdR llvm However, the file still exits. Henrik. >From: Reid Spencer >Date: Mon, 20 Jun 2005 10:57:54 -0700 > >Hi Henrik, > >You don't have the latest C/C++ Front End Source code. Please update >from CVS to get

Hi, I'm trying to test the llvm tools as described in 'http://llvm.cs.uiuc.edu/docs/TestingGuide.html'. However, when running the command: 'make check VERBOSE=1 2>&1' I get this error: ------------------- if test -d "/C/projects/build/MinGW/llvm-2-1/test" ; then \ if test -f "/C/projects/build/MinGW/llvm-2-1/test/Makefile" ; then \ echo

Now, I've no spaces in my path: ------------------ $ echo $PATH .:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread ------------------ I've found that you safely can delete site.exp. The new values in site.exp are: ------------------ ## these variables are automatically generated by make ## # Do not edit here.

Hello, LLVM community. I've built a cross-toolchain on Windows and I'm now trying to run unit tests for the LLVM libraries. I used Ninja as a build system and MSVC as host compiler without an issue, but when I try to run 'ninja check-llvm-unit', I get the following error: llvm-lit.py: C:/Users/sergej/Developer/llvm-project/llvm\utils\lit\lit\TestingConfig.py:102: fatal: unable

You're right. And no errors or results where generated: -------------------- if test -d "/C/projects/build/MinGW/llvm-2-1/test" ; then \ if test -f "/C/projects/build/MinGW/llvm-2-1/test/Makefile" ; then \ echo llvm[0]: Running test suite ; \ make -C /C/projects/build/MinGW/llvm-2-1/test check-local \ TESTSUITE= ; \ else \ echo llvm[0]: No Makefile in

>> 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 Fri, 7 Jan 2005, Henrik Bach wrote: > I'm trying to test the llvm tools as described in > 'http://llvm.cs.uiuc.edu/docs/TestingGuide.html'. The problem here is that your PATH envvar has spaces in it. There are many thing in LLVM that won't work with that, please try pruning your PATH and trying again. Thanks, -Chris > However, when running the command: 'make

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

>> Also I have in Makefile.rules (but not include in patch) some >> modification for simplify used common Makefile.rules in LLVM projects and >> non-LLVM project (guarding some LLVM specific parts by ifdef >> LLVM_OBJ_ROOT/LLVM_SRC_ROOT vars). > > I'm not sure about this, perhaps Reid would like to comment? > Patch attached. This patch with header

On Fri, Apr 11, 2008 at 3:24 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Lane Schwartz wrote: > > > [snip] > > > > OK then. I didn't realize that having a newer version would be a problem. > > > > I compiled and installed autoconf 2.59. I still get the same problem: > > > > $ autoconf --version > > autoconf (GNU Autoconf)

On Fri, 7 Jan 2005, Henrik Bach wrote: > "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread > llvm-gcc" > set llvmgxx >

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

> 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

On Mon, 7 Feb 2005, Vladimir Merzliakov wrote: >>> Also I have in Makefile.rules (but not include in patch) some modification >>> for simplify used common Makefile.rules in LLVM projects and non-LLVM >>> project (guarding some LLVM specific parts by ifdef >>> LLVM_OBJ_ROOT/LLVM_SRC_ROOT vars). >> >> I'm not sure about this, perhaps Reid

Hi! In current LLVM CVS: llvm/projects/Stacker/Makefile.common.in llvm/projects/sample/Makefile.common.in llvm-java/llvm-java/Makefile.common.in have line: include $(LLVM_OBJ_ROOT)/Makefile.common that have line: include $(LLVM_OBJ_ROOT)/Makefile.config (also $(LLVM_OBJ_ROOT)/Makefile.config used in llvm-test/Makefile.config.in) and llvm/Makefile.config.in have lines: INSTALL_SH :=

On Fri, 7 Jan 2005, Henrik Bach wrote: > You're right. And no errors or results where generated: > PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:/C/projects/src/llvm-2/llvm/test/Scripts:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread > \ > true runtest > make[1]: Leaving directory

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