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