similar to: Issues with Eclipse CDT4

Am 10.10.2015 um 21:14 schrieb Tim Northover: > On 10 October 2015 at 04:16, Joachim Durchholz via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> is this the right place to discuss getting LLVM built using Eclipse, >> as described on http://llvm.org/docs/GettingStarted.html? > > It's probably as good as anywhere, Okay. > but I don't think

Is anyone using Eclipse and gdb to debug llvm/clang? If so, which version of Eclipse, gdb and linux flavor. I just use gdb currently. I'm going to try using my mac also. Is anyone using xcode/lldb to debug llvm/clang? Tia. Reed

Hi Reed, I’ve used Eclipse for a long time to do LLVM development on Linux (both for code navigation/editing and debugging), any recent Linux distribution and version of Eclipse should be fine (even older versions should be good enough as this has been working for many years). Xcode works fine as well, I started to use Xcode exclusively when I switched to OS X. The key to make this work is to

Sorry if I'm repeating something that was already said. I was just thinking "why the heck do I seem headed for JVM generation if what I want to use is LLVM", and this is the result: I'm coming from a Java background. I'm using Eclipse, I'm used to the syntax highlighting, cross referencing and refactoring support that Eclipse offers. I know I will want to have the

On 07/16/2013 05:21 AM, Tilmann Scheller wrote: > Hi Reed, > > I’ve used Eclipse for a long time to do LLVM development on Linux (both for code navigation/editing and debugging), any recent Linux distribution and version of Eclipse should be fine (even older versions should be good enough as this has been working for many years). > > Xcode works fine as well, I started to use Xcode

Tilmann Scheller <tilmann.scheller at googlemail.com> writes: [snip] > It might be worth to put an Eclipse CDT project file with relative > paths to the header files in the LLVM SVN repository to make it easier > for people to use Eclipse in the future (my project files currently > contain absolute paths, so they're probably not useful to other > people). CMake can

Hi all, I checked out everything mentioned in GettingStarted at tags/RELEASE_370/final and ran `make -j4 check-all`. I got three test failures: libc++abi :: catch_array_01.pass.cpp libc++abi :: catch_function_01.pass.cpp libc++abi :: catch_member_function_pointer_01.pass.cpp Should I worry? Here are the failures as reported, with the LLVM source directory replaced with ... for

On 07/16/2013 05:21 AM, Tilmann Scheller wrote: > Hi Reed, > > I’ve used Eclipse for a long time to do LLVM development on Linux (both for code navigation/editing and debugging), any recent Linux distribution and version of Eclipse should be fine (even older versions should be good enough as this has been working for many years). > > Xcode works fine as well, I started to use Xcode

On 11 October 2015 at 21:46, Joachim Durchholz via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Since I plan to use LLVM as a backend, not hack on it, I'm not going to get > much joy out of TRUNK, so I reverted to 3.7. > Which led me to the realization that GettingStarted does not mention > libcxxabi. That depends on what you use. If you use libc++, then you need to worry

I have noticed that I was installing LLVM according to: http://llvm.org/docs/GettingStarted.html#getting-started so it was no the 3.1 but the 3.2 version from svn (trunk 167573). Maybe in the svn, not stable version, there is a bug? 2012/11/9 Wojciech Daniło <wojtek.danilo.ml at gmail.com> > Does anybody have Idea why I get such error? The LLVM is compiled from > source - is is the

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

Joachim Durchholz wrote: > Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner: > >> 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

Am Donnerstag, den 20.03.2008, 15:27 -0700 schrieb Shantonu Sen: > llvm's ./configure already does that for gcc < 3. > > What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2? There's a list at http://llvm.org/docs/GettingStarted.html#brokengcc so there is a reasonable basis. The list isn't comprehensive, of course, and will likely grow in the future. OTOH

>> 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 >>

If anyone is interested in this topic, I filled a bug here: http://llvm.org/bugs/post_bug.cgi 2012/11/9 Wojciech Daniło <wojtek.danilo.ml at gmail.com> > I have noticed that I was installing LLVM according to: > http://llvm.org/docs/GettingStarted.html#getting-started > so it was no the 3.1 but the 3.2 version from svn (trunk 167573). > Maybe in the svn, not stable version,

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.

Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner: > 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? uname

Hi Just thought I might ask my recent question about Eclipse again, only in a slightly different way: Is anyone here using the Eclipse version supplied with the CentOS 6 distro (as opposed to a build downloaded from www.eclipse.org)? Does it work for you? Are you able to install additional components via the built-in software setup mechanism? Thanks, - Toralf This e-mail, including any

I recommend you don't parse version strings. In fact I switch the check to use AC_COMPILE precisely for the reason that gcc --version is totally unreliable and vendor specific. For example, what's the regular expression that tells you what the GCC version is: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5470) (Aspen 5470.3) Per the rest of this thread, you can't

Has anyone tried using the Eclipse CDT plugin (or another C++ IDE) to develop code in LLVM? I'm specifically interested in getting code completion to work. --Patrick