similar to: [LLVMdev] make error building llvm/clang 3.2 on Linux

Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] make error building llvm/clang 3.2 on Linux"

2013 Feb 26
2
[LLVMdev] make error building llvm/clang 3.2 on Linux
Just in case someone is having similar problems and/or following this thread, here's my final "solution" (at least, for now). In my bash build script, prior to configure, I set the C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to empty strings, and then set some other environment variables instead: export C_INCLUDE_PATH= export CPLUS_INCLUDE_PATH=
2013 Feb 24
0
[LLVMdev] make error building llvm/clang 3.2 on Linux
I'm continuing this here in llvm-dev since the thread was started here, but, in hindsight, it may have been better in cfe-dev, because the problem seems to be related to clang. I turned on "verbose" mode in make (VERBOSE=1 TOOL_VERBOSE=1) and found that it is clang, not gcc, that is being used at this point in the make. Based on the command issued (particularly with the --sysroot
2013 Feb 26
0
[LLVMdev] make error building llvm/clang 3.2 on Linux
Hi Michael, you don't need compiler-rt to use clang. If you don't need it, I suggest you don't bother building it. Ciao, Duncan. On 21/02/13 01:15, Michael Young wrote: > > I'm attempting to build a native build of clang from the 3.2 source > distribution tarballs, but I ran into this build error that's got me > really puzzled. My platform is Linux - 32-bit
2013 Feb 26
0
[LLVMdev] LLVM/clang 3.2 build error on Linux
I'm posting this here to document what I encountered and the solution I found, in hopes that others may find it useful. When building clang 3.2 on Linux (Ubuntu 12.04, 32-bit, x86 PC), I received the following errors (messages from the make output): ... make[4]: Entering directory `/home/youngmj/DevTools/LLVM/Version_3.2/build/tools/clang/runtime/compiler-rt' /bin/sh: 1:
2011 Mar 22
4
[LLVMdev] -emit-llvm on ubuntu is broken
Hi Eric, here is my -emit-llvm -S -v output: Using built-in specs. COLLECT_GCC=gcc-4.5 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.1-7ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
2011 Mar 22
0
[LLVMdev] -emit-llvm on ubuntu is broken
Looks like something wonky with DragonEgg. Duncan? -eric On Mar 21, 2011, at 7:05 PM, stackunderflow wrote: > > Hi Eric, > > here is my -emit-llvm -S -v output: > > Using built-in specs. > COLLECT_GCC=gcc-4.5 > COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper > Target: i686-linux-gnu > Configured with: ../src/configure -v
2011 Mar 22
0
[LLVMdev] -emit-llvm on ubuntu is broken
On Mar 21, 2011, at 6:36 PM, stackunderflow wrote: > > I try to generate a human readable .ll file on Linux. I installed llvm-gcc > but as I see it can generate only assembly code (-S option). Is there any > way to get something like what is generated by llvm online compiler? > > That's what I get with llvm-gcc -S -emit-llvm hello.c on Ubuntu 10.10: llvm-gcc -v ? -eric
2011 Mar 22
2
[LLVMdev] -emit-llvm on ubuntu is broken
Hi Eric, > Looks like something wonky with DragonEgg. you need to use -fplugin-arg-dragonegg-emit-ir or -flto with dragonegg, not -emit-llvm. Also, you currently have to use -S (getting human readable IR) rather than -c because with -c gcc will run cc1 with -S (getting human readable IR) then pass the result to the system assembler which of course barfs. This is documented on the web-page
2017 Dec 26
2
Regression tests
Hello, I have just built LLVM with CMake by following these instructions https://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary and I am trying to run the regression tests using "make check-all" but there are some unexpected failures in libcxx and libcxxabi. Here's the test log: Expected Passes : 40745 Expected Failures : 258 Unsupported Tests : 1594
2011 Mar 22
2
[LLVMdev] -emit-llvm on ubuntu is broken
I try to generate a human readable .ll file on Linux. I installed llvm-gcc but as I see it can generate only assembly code (-S option). Is there any way to get something like what is generated by llvm online compiler? That's what I get with llvm-gcc -S -emit-llvm hello.c on Ubuntu 10.10: .file "hello.c" .ident "GCC: (Ubuntu/Linaro 4.5.1-7ubuntu2) 4.5.1 LLVM: "
2012 Jul 18
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Wed, Jul 18, 2012 at 4:15 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 14:57, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> $ clang -march=armv7-m -mfloat-abi=soft -ccc-host-triple >> armv7m-none-gnueabi testReference.cpp -c >> fatal error: error in backend: CPU: 'cortex-m3' does not support ARM >>
2012 Jul 18
3
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 18 July 2012 14:57, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > $ clang -march=armv7-m -mfloat-abi=soft -ccc-host-triple > armv7m-none-gnueabi testReference.cpp -c > fatal error: error in backend: CPU: 'cortex-m3' does not support ARM > mode execution! Ah, yes! Try: $ clang -ccc-host-triple thumbv7m-none-gnueabi testReference.cpp -c Cross
2012 Jul 18
2
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 18 July 2012 15:24, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > I'm not sure how to interpret the above output, but I don't understand > why if say -triple armv4t-none--gnueabi . Ok, we're getting there... ;) I think these errors are due to Clang not finding the libraries/includes/etc for the target you're building. If you have
2012 Oct 21
0
[LLVMdev] dragonegg polly support broken?
On 10/20/2012 05:38 PM, Jack Howarth wrote: > Duncan, > Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg > using the documentation at http://polly.llvm.org/example_load_Polly_into_dragonegg.html > with... > > GCC=/sw/lib/gcc4.7/bin/gcc-4 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config ENABLE_LLVM_PLUGINS=1 make
2012 Oct 21
2
[LLVMdev] dragonegg polly support broken?
Duncan, Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg using the documentation at http://polly.llvm.org/example_load_Polly_into_dragonegg.html with... GCC=/sw/lib/gcc4.7/bin/gcc-4 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config ENABLE_LLVM_PLUGINS=1 make CPPFLAGS="-DENABLE_LTO -I/sw/include" The resulting dragonegg plugin works fine
2014 Feb 03
1
Fwd: linker issue
Hi, I am trying to compile C++ with R and I am coming up against - what I believe - is a linker configuration issue. For example, using has_develop() gives the following message... > has_devel() "C:/PROGRA~1/R/R-30~1.2/bin/i386/R" --vanilla CMD SHLIB foo.c gcc -m32 -I"C:/PROGRA~1/R/R-30~1.2/include" -DNDEBUG -I"d:/RCompile/CRANpkg/extralibs64/local/include"
2014 Apr 28
1
Will Devtools-1.1 or later become part of SCL?
I've already installed devtools-1.1 from Tru Huynh. http://people.centos.org/tru/devtools-1.1/ Thank You Tru. gcc 4.7.2 is so much newer than stock 4.4.7. (much better C++11 support) Why is devtools-1.1 not officially part of CentOS SCL? I know devtools-2.0 still has issues but 1.1 would bring us on par with Debian 7.0. http://wiki.centos.org/AdditionalResources/Repositories/SCL
2017 Oct 10
2
Cannot install igraph package
On Mon, Oct 9, 2017 at 4:42 PM, Tom Callaway <tcallawa at redhat.com> wrote: > > On 10/09/2017 11:16 AM, Paul Smith wrote: >> >> I am trying to install >> >> igraph package >> >> but getting the following error: >> >> ------------------ >> make: *** [/usr/lib64/R/etc/Makeconf:159: foreign-graphml.o] Error 1 >> ERROR:
2020 Oct 31
2
R 4.0 for CentOS 7
On 10/30/2020 05:02 AM, I?aki Ucar wrote: > Please, do not crosspost. As I said in the Bugzilla issue, R cannot be > further updated in EPEL-7, see > https://bugzilla.redhat.com/show_bug.cgi?id=1871685#c2. > > I?aki > > > On Fri, 30 Oct 2020 at 02:30, H <agents at meddatainc.com> wrote: >> I am running R 4.6 under CentOS 7 but would like to upgrade. Just found
2018 Jan 03
0
Regression tests
Re-adding the dev list. It's best to always keep the discussions on the list. Don't worry about the length of the message, you need to communicate the information that is important to describe your problem. So I am not the best person to answer this question since I don't build/test libcxx or libcxxabi, but I'm sure there are plenty of people on the list that are quite