llvm dev - Dec 2009 - [LLVMdev] Problem running 2.6 test-suite on cygwin

On Sun, Dec 13, 2009 at 11:34 AM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>> LLVM tools and LLVM-GCC I've built seem to work.
>> Can it be due to LLVM_SRC_ROOT == LLVM_OBJ_ROOT?
> No. This is usually due to absence of llvm-gcc. You need reconfigure
> llvm once again with lvm-gcc path added and make sure it was hooked
> properly (look into Makefile.config for paths, etc).
As I mentioned, it looks like llvm-gcc is installed properly. From
Makefile.config:

LLVMGCC  := /usr/local/bin/llvm-gcc.exe
LLVMGXX  := /usr/local/bin/llvm-g++.exe
LLVMCC1  := /usr/local/libexec/gcc/i686-pc-cygwin/4.2.1/cc1.exe
LLVMCC1PLUS := /usr/local/libexec/gcc/i686-pc-cygwin/4.2.1/cc1plus.exe
LLVMGCC_VERSION := 4.2.1
LLVMGCC_MAJVERS := 4
LLVMGCC_LANGS := c,c++

It looks to me that this:

make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc',
needed by `Output/sse.expandfft.linked.bc'.  Stop.

means that make is trying to build this (from Makefile.programs):

# Given an unoptimized bytecode file that is a simple linkage of all
# the program's bytecode files, optimize the program using the
# standard compilation optimizations.
$(PROGRAMS_TO_TEST:%=Output/%.linked.bc): \
Output/%.linked.bc: Output/%.linked.rbc $(LOPT)
        $(VERB) $(RM) -f $(CURDIR)/$@.info
        -$(LOPT) -std-compile-opts -info-output-file=$(CURDIR)/$@.info
$(STATS) $(EXTRA_LOPT_OPTIONS) $< -o $@ -f

But for some strange reason it can't find this rule (from
Makefile.singlesrc):

Output/%.linked.rbc: Output/%.bc
        -cp -f $< $@

What can be a reason for this?

                Gregory

On Sun, Dec 13, 2009 at 4:34 PM, Gregory Petrosyan
<gregory.petrosyan at gmail.com> wrote:
> On Sun, Dec 13, 2009 at 11:34 AM, Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
>>> LLVM tools and LLVM-GCC I've built seem to work.
>>> Can it be due to LLVM_SRC_ROOT == LLVM_OBJ_ROOT?
>> No. This is usually due to absence of llvm-gcc. You need reconfigure
>> llvm once again with lvm-gcc path added and make sure it was hooked
>> properly (look into Makefile.config for paths, etc).
I forgot to add: I have done roughly the following:

1) configure llvm with --enable-optimitzed --enable-targets=x86
2) build llvm with "make tools-only"
3) installed llvm
4) configured llvm-gcc
5) build llvm-gcc
6) installed llvm-gcc

Sidenote: after this step, all of LLVM tools and LLVM-GCC are in the
PATH, and they appear to work: I can compile, link, optimize,
disassemble, etc.

7) re-configured llvm (without --with-llvmgccdir, because llvm-gcc is
in the PATH)
8) build llvm
9) try to "make" the test-suite

Have I missed anything?

LLVM, LLVM-GCC and test-suite are all from 2.6 svn branch.

                Gregory

> It looks to me that this:
>
> make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc',
> needed by `Output/sse.expandfft.linked.bc'.  Stop.
Well, I have no idea then. makefiles of testsuite are well-known for
such erratic behavior :(

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Sun, Dec 13, 2009 at 8:17 PM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>> It looks to me that this:
>>
>> make[4]: *** No rule to make target
`Output/sse.expandfft.linked.rbc',
>> needed by `Output/sse.expandfft.linked.bc'.  Stop.
> Well, I have no idea then. makefiles of testsuite are well-known for
> such erratic behavior :(
For the record: LLVM trunk starts test-suite, but reports lots of
failures and then (predictably) hangs eating 100% CPU. I'll try a bit
more with cygwin, and in case I'll be unable to make it work I'll
switch to linux.

                Gregory