I am getting an "--emit-llvm is not supported in this configuration"
error on a release build on Cygwin, the debug build is fine.
make[3]: Entering directory `/usr/build/llvm/runtime/GCCLibraries/libc'
llvm[3]: Compiling atox.c for Release build (bytecode)
llvm-gcc: --emit-llvm is not supported in this configuration.
make[3]: *** [/usr/build/llvm/runtime/GCCLibraries/libc/Release/atox.ll]
Error 1
This is the same error that appears alot of times on the 'make check' of
the debug build.
What is going on here please ?
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20070228/f67b1e01/attachment.html>
Aaron, On Wed, 2007-02-28 at 15:40 +0000, Aaron Gray wrote:> I am getting an "--emit-llvm is not supported in this configuration" > error on a release build on Cygwin, the debug build is fine. > > make[3]: Entering directory > `/usr/build/llvm/runtime/GCCLibraries/libc' > llvm[3]: Compiling atox.c for Release build (bytecode) > llvm-gcc: --emit-llvm is not supported in this configuration. > make[3]: *** > [/usr/build/llvm/runtime/GCCLibraries/libc/Release/atox.ll] Error 1 > > This is the same error that appears alot of times on the 'make check' > of the debug build. > > What is going on here please ?Sounds to me like the llvm-gcc being used wasn't configured using --with-llvm=. That message occurs when llvm-gcc is built "normally" (without using llvm).> Aaron > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
I did not realize that '--enable-llvm' was required and that invalidates my debug build results which were built just with LLVM on the path. I am now getting a segmentation fault when doing a 'make install' on LLVM-GCC4, possibly validating my original thoughts that GCC 4.1.1 was required to build LLVM-GCC 4.0.1. I will try using GCC 4.1.1. Heres the error anyway :- make[2]: Entering directory `/usr/build/llvm-gcc4/gcc' /usr/build/llvm-gcc4/gcc/xgcc -B/usr/build/llvm-gcc4/gcc/ -B/usr/llvm-gcc4/i686- pc-cygwin/bin/ -B/usr/llvm-gcc4/i686-pc-cygwin/lib/ -isystem /usr/llvm-gcc4/i686 -pc-cygwin/include -isystem /usr/llvm-gcc4/i686-pc-cygwin/sys-include -O2 -I/usr /src/llvm-gcc4/gcc/../winsup/w32api/include -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./inc lude -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/usr/src/llvm-gcc4/g cc -I/usr/src/llvm-gcc4/gcc/. -I/usr/src/llvm-gcc4/gcc/../include -I/usr/src/llv m-gcc4/gcc/../libcpp/include -I/usr/src/llvm/include -I/usr/build/llvm/include -DL_eprintf -c /usr/src/llvm-gcc4/gcc/libgcc2.c -o libgcc/./_eprintf.o /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://llvm.org/bugs> for instructions. make[2]: *** [libgcc/./_eprintf.o] Error 1 make[2]: Leaving directory `/usr/build/llvm-gcc4/gcc' make[1]: *** [libgcc.a] Error 2 make[1]: Leaving directory `/usr/build/llvm-gcc4/gcc' make: *** [install-gcc] Error 2 ----- Original Message ----- From: "Reid Spencer" <rspencer at reidspencer.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Wednesday, February 28, 2007 4:15 PM Subject: Re: [LLVMdev] Cygwin release build error> Aaron, > > On Wed, 2007-02-28 at 15:40 +0000, Aaron Gray wrote: >> I am getting an "--emit-llvm is not supported in this configuration" >> error on a release build on Cygwin, the debug build is fine. >> >> make[3]: Entering directory >> `/usr/build/llvm/runtime/GCCLibraries/libc' >> llvm[3]: Compiling atox.c for Release build (bytecode) >> llvm-gcc: --emit-llvm is not supported in this configuration. >> make[3]: *** >> [/usr/build/llvm/runtime/GCCLibraries/libc/Release/atox.ll] Error 1 >> >> This is the same error that appears alot of times on the 'make check' >> of the debug build. >> >> What is going on here please ? > > Sounds to me like the llvm-gcc being used wasn't configured using > --with-llvm=. That message occurs when llvm-gcc is built > "normally" (without using llvm). > >> Aaron >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.446 / Virus Database: 268.18.4/705 - Release Date: 27/02/2007 15:24 >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070228/e5d8c9fe/attachment.html>
Hello, Aaron.> /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': > /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://llvm.org/bugs> for instructions.You should: 1. Try to emit bytecode with --emit-llvm compiler switch. 1.1 If you'll obtained bytecode - use llc to check, whether the problem exists and after reduce bytecode via bugpoint 2. If it fails even with bytecode emission - 2.1 Try to do everything with -O0 compiler switch. 2.2 Otherwise - try to gdb cc1 to find the place of segfault. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
Hi Anton & Reid, This is still at the stage of using xgcc.exe AFAICT before any LLVM bytecode generation. __eprintf is a very simple function so I do not know what could be wrong here. I'll give it some time and thought before filing a bug report. I maybe doing something else basic wrong. It is a shame about GCC 4.1.1. Though it looks like I may well be stuck with getting LLVM-GCC4 built on Cygwin. Any advice welcome. Aaron ----- Original Message ----- From: "Anton Korobeynikov" <asl at math.spbu.ru> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Wednesday, February 28, 2007 8:46 PM Subject: Re: [LLVMdev] Cygwin release build error> Hello, Aaron. > >> /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': >> /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: >> Segmentation fault >> Please submit a full bug report, >> with preprocessed source if appropriate. >> See <URL:http://llvm.org/bugs> for instructions. > You should: > 1. Try to emit bytecode with --emit-llvm compiler switch. > 1.1 If you'll obtained bytecode - use llc to check, whether the problem > exists and after reduce bytecode via bugpoint > 2. If it fails even with bytecode emission - > 2.1 Try to do everything with -O0 compiler switch. > 2.2 Otherwise - try to gdb cc1 to find the place of segfault. > > -- > With best regards, Anton Korobeynikov. > > Faculty of Mathematics & Mechanics, Saint Petersburg State University. > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.446 / Virus Database: 268.18.4/705 - Release Date: 27/02/2007 > 15:24 >
Hello, Aaron.> This is still at the stage of using xgcc.exe AFAICT before any LLVM bytecode > generation.Yep. But xgcc generates code via LLVM! So, you can just copy command line from your terminal, add -emit-llvm, run it and you'll see, that resulting .o will be LLVM bytecode (or won't if FE will crash).> __eprintf is a very simple function so I do not know what could be wrong > here.Anything, actually. libgcc is the first target of misc. codegen-related crashes, because it's the first code being compiled with newly-built llvm-gcc. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
Anton,> Hello, Aaron. > >> This is still at the stage of using xgcc.exe AFAICT before any LLVM >> bytecode >> generation. > Yep. But xgcc generates code via LLVM! So, you can just copy command > line from your terminal, add -emit-llvm, run it and you'll see, that > resulting .o will be LLVM bytecode (or won't if FE will crash).Okay that works, got a _eprintf.o file. Also works without the -emit-llvm !! But crashes when called from the make file. Weird. Aaron
Hello, Aaron.> Once made the make file goes on to the next file produced (also from) > libgcc2.c !!!Yep. libgcc is nifty: it contains many small chunks of form #ifdef func1 ... #endif #ifdef func2 ... #endif So, almost everything is building from the same libgcc2.c source -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.