Joachim Durchholz
2008-Mar-20 22:00 UTC
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Hi all, I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the (broken-for-LLVM) gcc-4.1 as a compiler. The error message that I got was this: make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' make[1]: *** No rule to make target `/home/jo/llvm-wrk/Release/bin/tblgen', needed by `/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop. make[1]: Leaving directory `/home/jo/llvm-wrk/lib/VMCore' make: *** [install] Error 1 It took me a while to figure out what went wrong. I guess I'm not the only one to stumble upon this problem. Would it be a good idea to make ./configure check whether there's an incompatible tool configured, and carp if it finds one? Regards, Jo
Eric Christopher
2008-Mar-20 22:14 UTC
[LLVMdev] Just got bitten by accidentally using the wrong gcc
On Mar 20, 2008, at 3:00 PM, Joachim Durchholz wrote:> Hi all, > > I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the > (broken-for-LLVM) gcc-4.1 as a compiler. > The error message that I got was this: > make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' > make[1]: *** No rule to make target > `/home/jo/llvm-wrk/Release/bin/tblgen', needed by > `/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop. > make[1]: Leaving directory `/home/jo/llvm-wrk/lib/VMCore' > make: *** [install] Error 1 > > It took me a while to figure out what went wrong. > > I guess I'm not the only one to stumble upon this problem. > > Would it be a good idea to make ./configure check whether there's an > incompatible tool configured, and carp if it finds one?Probably be a good idea. It's reasonably easy to check major/minor versions. -eric
Shantonu Sen
2008-Mar-20 22:27 UTC
[LLVMdev] Just got bitten by accidentally using the wrong gcc
llvm's ./configure already does that for gcc < 3. What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2? dnl Verify that GCC is version 3.0 or higher if test "$GCC" = "yes" then AC_COMPILE_IFELSE([[#if !defined(__GNUC__) || __GNUC__ < 3 #error Unsupported GCC version #endif ]], [], [AC_MSG_ERROR([gcc 3.x required, but you have a lower version])]) fi Shantonu Sen ssen at apple.com Sent from my Mac Pro On Mar 20, 2008, at 3:14 PM, Eric Christopher wrote:> > On Mar 20, 2008, at 3:00 PM, Joachim Durchholz wrote: >> Hi all, >> >> I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the >> (broken-for-LLVM) gcc-4.1 as a compiler. >> The error message that I got was this: >> make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' >> make[1]: *** No rule to make target >> `/home/jo/llvm-wrk/Release/bin/tblgen', needed by >> `/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop. >> make[1]: Leaving directory `/home/jo/llvm-wrk/lib/VMCore' >> make: *** [install] Error 1 >> >> It took me a while to figure out what went wrong. >> >> I guess I'm not the only one to stumble upon this problem. >> >> Would it be a good idea to make ./configure check whether there's an >> incompatible tool configured, and carp if it finds one? > > Probably be a good idea. It's reasonably easy to check major/minor > versions. > > -eric > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Tanya M. Lattner
2008-Mar-20 22:44 UTC
[LLVMdev] Just got bitten by accidentally using the wrong gcc
>> I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the >> (broken-for-LLVM) gcc-4.1 as a compiler. >> The error message that I got was this: >> make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' >> make[1]: *** No rule to make target >> `/home/jo/llvm-wrk/Release/bin/tblgen', needed by >> `/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop. >> make[1]: Leaving directory `/home/jo/llvm-wrk/lib/VMCore' >> make: *** [install] Error 1 >> >> It took me a while to figure out what went wrong. >> >> I guess I'm not the only one to stumble upon this problem. >> >> Would it be a good idea to make ./configure check whether there's an >> incompatible tool configured, and carp if it finds one? > > Probably be a good idea. It's reasonably easy to check major/minor > versions.Its not just a matter of checking major/minor versions. It also depends on the target and in some cases the OS. http://llvm.org/docs/GettingStarted.html#brokengcc So for example, GCC 3.3.3 on Suse or GCC 3.4.0 on linux/x86 (32-bit) has issues. Is it easy to check these kinds of things? Do we even want to? I guess it could be done for things like 4.1.1 or a couple of others on the list. -Tanya
Possibly Parallel Threads
- [LLVMdev] Just got bitten by accidentally using the wrong gcc
- [LLVMdev] Just got bitten by accidentally using the wrong gcc
- [LLVMdev] Just got bitten by accidentally using the wrong gcc
- [LLVMdev] Just got bitten by accidentally using the wrong gcc
- [LLVMdev] Just got bitten by accidentally using the wrong gcc