[LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4

Duncan Sands baldrick at free.fr
Wed Nov 23 12:02:55 PST 2011 

On 23/11/11 20:35, Harris, Kevin wrote:
> In response to:
>  > Date: Wed, 23 Nov 2011 18:24:16 +0100
>  > From: Duncan Sands <baldrick at free.fr <mailto:baldrick at free.fr>>
>  > Subject: Re: [LLVMdev] Follow-up questions after successful upgrade to
>  > LLVM 3.0rc4
>  > To: llvmdev at cs.uiuc.edu <mailto:llvmdev at cs.uiuc.edu>
>  > Hi Kevin,
>  >> Since I don’t have llvm-gcc installed, I tried to do the configure by doing a
>  >> “cd” to the test-suite directory
>  >> and just doing a “./configure”.
>  >
>  > the configure should be done in the directory where you built LLVM.
> Thanks! I tried doing:

You need to put the testsuite in llvm/projects, with the directory named
either llvm-test or test-suite.  Do this before running configure.

>  > cd llvm30/build
>  > ../test-suite-3.0rc4.src/configure
> . . . configure output

At this point you need to go deeper in the build directory:
   cd projects/llvm-test
(or cd projects/test-suite if you called it that).

This is where you run make.

Ciao, Duncan.

>  > cd ../test-suite-3.0rc4.src
>  > gmake LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1
> And got the same error as I described previously. On the assumption that my
> flailing around had
> contaminated my environment, I decided to start from scratch with the
> test-suite. So I deleted
> the test-suite directory, downloaded it again, unpacked it, and retried this
> same set of commands.
> Again, the configure appears to execute normally.
> This time I get a similar, but not identical error:
> Makefile.common:13: Makefile.config: No such file or directory
> Makefile.common:19: /Makefile.rules: No such file or directory
> gmake: *** No rule to make target `/Makefile.rules'. Stop.
> This error appears whether I use the options or not, and whether or not I give
> it a target, like
> “report” or “clean”.
> Just for grins, I also tried using the LLVMCC_OPTION and ENABLE_BUILT_CLANG
> options on the
> configure step, rather than on the “gmake” step. The configure didn’t seem to
> mind, but neither
> did it do anything different. The same error appears on any attempt to do a
> “gmake” or “make”.
> I have the LLVM 3.0rc4 and the clang from the same kit built and installed in my
> llvm30 directory, and they
> appear to be working normally. Any idea what I’m doing wrong? Is there a
> description of the use
> of this configure script available?
> If it helps, here’s the output of the configure step:
> kharris at linux-crzw:~/llvm30/build> ../test-suite-3.0rc4.src/configure
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> checking type of operating system we're going to target... Linux
> checking target architecture... x86_64
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking whether byte ordering is bigendian... no
> checking clang compiler... none
> checking LLVM capable compiler... none
> checking for llvm-gcc... no
> checking for llvm-g++... no
> checking whether llvm-gcc is dragonegg... no
> checking whether llvm-gcc is sane... no
> checking for spec95 benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/spec95/benchspec
> checking for spec2000 benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/speccpu2000/benchspec
> checking for spec2006 benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/speccpu2006/benchspec
> checking for povray benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/povray31
> checking for namd benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/spec_namd
> checking for sweep3d benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/sweep3d
> checking for fpgrowth benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/fpgrowth
> checking for alp benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/alp
> checking for nurbs benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/nurbs
> checking for hmmer benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/hmmer
> checking for skidmarks10 benchmark sources... no, not found in
> /home/kharris/projects/test-suite-externals/skidmarks10
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking how to run the C preprocessor... gcc -E
> checking for GNU make... make
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld
> checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
> checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for f77... no
> checking for xlf... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether accepts -g... no
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64)
> supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating mklib
> appending configuration tag "CXX" to mklib
> checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64
> checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU
> ld... yes
> checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64)
> supports shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64)
> supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to mklib
> checking for f2c bin/lib/include locations... no
> checking for nag-fortran bin/lib/include locations... no
> checking sanity for program f95... not found
> checking for sys/wait.h that is POSIX.1 compatible... yes
> checking for compiler -Wl,-R<path> option... yes
> checking for re_comp... yes
> checking which extension is used for loadable modules... .so
> configure: creating ./config.status
> config.status: creating Makefile.config
> config.status: executing setup commands
> config.status: executing Makefile commands
> config.status: executing Makefile.common commands
> config.status: executing Makefile.nagfortran commands
> config.status: executing Makefile.f2c commands
> config.status: executing Makefile.programs commands
> config.status: executing Makefile.tests commands
> config.status: executing TEST.aa.Makefile commands
> config.status: executing TEST.aa.report commands
> config.status: executing TEST.example.Makefile commands
> config.status: executing TEST.nightly.Makefile commands
> config.status: executing TEST.buildrepo.Makefile commands
> config.status: executing TEST.jit.Makefile commands
> config.status: executing TEST.nightly.report commands
> config.status: executing TEST.jit.report commands
> config.status: executing TEST.typesafe.Makefile commands
> config.status: executing TEST.vtl.Makefile commands
> config.status: executing External/Makefile commands
> config.status: executing External/Makefile.external commands
> config.status: executing External/Povray/Makefile commands
> config.status: executing External/SPEC/Makefile commands
> config.status: executing External/SPEC/Makefile.spec commands
> config.status: executing External/SPEC/Makefile.spec.config commands
> config.status: executing External/SPEC/Makefile.spec2006 commands
> config.status: executing External/SPEC/Makefile.spec2000 commands
> config.status: executing External/SPEC/Makefile.spec95 commands
> config.status: executing External/SPEC/CFP2006/Makefile commands
> config.status: executing External/SPEC/CINT2006/Makefile commands
> config.status: executing External/SPEC/CFP2000/Makefile commands
> config.status: executing External/SPEC/CINT2000/Makefile commands
> config.status: executing External/SPEC/CFP95/Makefile commands
> config.status: executing External/SPEC/CINT95/Makefile commands
> config.status: executing External/skidmarks10/Makefile commands
> config.status: executing MultiSource/Makefile commands
> config.status: executing MultiSource/Makefile.multisrc commands
> config.status: executing SingleSource/Makefile commands
> config.status: executing SingleSource/Makefile.singlesrc commands
> config.status: executing tools/Makefile commands
> One interesting tidbit: One of the lines is: “checking clang compiler … none”,
> and yet, I can do:
> kharris at linux-crzw:~/llvm30/test-suite-3.0rc4.src> clang -v
> clang version 3.0 (tags/RELEASE_30/rc4)
> Target: x86_64-unknown-linux-gnu
> Thread model: posix
> Ideas?
> Thanks again!
> -Kevin
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

More information about the llvm-dev mailing list