similar to: [LLVMdev] Problem compiling llvm-gcc

Hi All, I recently ran into an issue that was posted several years back on LLVMdev [1]. A brief recap of the problem is that when cross-compiling LLVM itself the configure/make scripts get confused when creating the needed build host tools. For example, building and configuring like: CC_FOR_BUILD='i686-pc-linux-gnu-gcc' CXX_FOR_BUILD='i686-pc-linux-gnu-g++'

Thanks for the quick answer! Syncing to r61112 got rid of the ICE, but I still get the following error: make "DESTDIR=" "RPATH_ENVVAR=DYLD_LIBRARY_PATH" "TARGET_SUBDIR=i686-apple-darwin9" "bindir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/bin" "datadir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/share"

Holger Schurig wrote: [snip] > ../../../../llvm-gcc/libstdc++-v3/src/istream.cc:495: internal compiler > error: Segmentation fault I encountered the same error and the nice people from the llvm irc-channel suggested the attached patch. It enables compiling llvm-gcc for me, but i have not yet done any further testing and i also have no idea if this is the right way to fix the problem.

On 06/26/17 14:42, Timo Sirainen wrote: > On 26 Jun 2017, at 23.19, Marc Perkel <marc at perkel.com> wrote: >> Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. >> >> I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. >> >> I'm running Centos

I'm on OSX 10.5, trying to build a svn checkout of llvm-gcc. I've also checked out llvm. Both are synced to r61075. I'm using Apple's gcc 4.0.1: $ gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /var/tmp/gcc/gcc-5488~2/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++

On Dec 16, 2008, at 10:34 AM, Jeffrey Yasskin wrote: > I'm on OSX 10.5, trying to build a svn checkout of llvm-gcc. I've also > checked out llvm. Both are synced to r61075. hi Jeffrey, This patch should have fixed the problem: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20081215/071210.html Please update and try again, sorry for the breakage! -Chris

On Fri, Apr 08, 2011 at 08:28:27AM +0200, Duncan Sands wrote: > Hi Jack, > > > The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn > > (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the > > build fails as... > > what does the command > ./TargetInfo -p > return (the TargetInfo program

Hi Dimitry, I do not particularly need to build libc++ from the package. Is the name of the package's libc++, libcxx, because this is where the installation starts finding undefined references, during linking CXX shared library ../../../lib/libc++.so. Please check below the first part of the log when the first error appear, I omited repeating results. Furthermore, the undefined references are

On 07/05/17 13:25, Aki Tuomi wrote: >> I use mbox compressed by gzip as read-only folder (using zlib plugin). >> >> I have errors in logs: >> Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion >> failed: (ret == -1) ... >> The bug appeared in 2.2.26 and still can be reproduced (in 2.2.31) >> >> Using 'git bisect' was not

Hello. I wrote the hook function for deliver. I want to add support of editheaders in the plug-in for dovecot. For this purpose I wrote the function rarules_get_stream. Remover of headrs works properly, but adding does not work. I took Timo Sirainen's advice from http://markmail.org/message/skb6arnll5gaopdr . Do I use a correct way of creation of a message? I give backtrace and a

On Wed, 22 Aug 2007, Ryan M. Lefever wrote: > I checked llvm-gcc 4.0 out from svn yesterday and am compiling it on 3 > different machines. I was able to compile it on 2 of the machines, but > the compilation failed on the third machine with the errors below. The > machine that the compilation failed on is running Fedora Core 4. The > processor is a AMD Athlon(tm) 64 Processor

This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My

Hi Ioannis, Just delete the projects/libcxx directory, then rebuild from scratch. You should only need to checkout llvm (in the top level directory) and cfe (into the tools/clang subdirectory). -Dimitry > On 29 Mar 2016, at 00:08, Ioannis Koukoulis <i.g.koukoulis at gmail.com> wrote: > > Hi Dimitry, > > I do not particularly need to build libc++ from the package. Is the

Hello xapian users, The server I'm compiling on is a little odd. SunOS on a sun4 architecture. Fails when linking, gives the following, memcpy 0x10 /usr/local/gcc-3.3.2/lib/./libstdc++.a(ctype.o) ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status *** Error code 1 make: Fatal error:

Hi USing git, I reach the following error (below). Here is my configure parameters : CPPFLAGS="-I/include -I/usr/include/tirpc/" LDFLAGS="-L/lib -ltirpc" ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexec=/usr/libexec --with-sql=yes --without-sqlite --with-mysql --with-ssl --without-shadow --without-nss --without-pam --without-ldap --with-zlib

Chris, I'm a little confused. I am experiencing a crash when compiling the llvm-gcc frontend. According to the bugpoint documentation, bugpoint is used to debug "optimizer crashes, miscompilations by optimizers, or bad native code generation," which seems like it implies that the frontend compiles. Also, the http://llvm.org/docs/HowToSubmitABug.html documentation seems to

> > Is this behavior cured, or do you continue to see it? > No, the behavior isn't cured. We still continue to see it with various clients. I have posted a couple of truss outputs, but so far no resolution. Sorry for the slow response. I've been "fighting other fires". Jackie > Jackie Hunt wrote: > >> On Mon, 2007-09-03 at 12:37 +0200, Robert

Hi Dimitry, this definitely worked. I am passed by the linking errors regarding libc++ or similar. My build stopped now at 95% while linking a clang extra, I am not pretty sure which because i do not have my laptop, possible the clang-rename, if such exists. No undefined references here, however, my hdd's free space run out, so this might be the cause. I have to move or expand now, alas!! The

Hi, I'm trying to track down some nasty glibc failures on Linux. I think the problem is that my system compiler (3.4.6) doesn't match llvm-gcc (4.0.x) so when the llc compiled programs run they don't quite get the right libstdc++. If I run a test program with: LD_LIBRARY_PATH=/path/to/my/llvm-gcc4/libs Output/sieve.llc then I get this: Output/sieve.llc: symbol lookup error:

I checked llvm-gcc 4.0 out from svn yesterday and am compiling it on 3 different machines. I was able to compile it on 2 of the machines, but the compilation failed on the third machine with the errors below. The machine that the compilation failed on is running Fedora Core 4. The processor is a AMD Athlon(tm) 64 Processor 3700+. The version of gcc I have on the machine is 4.0.2. I tried