similar to: building a libR.a for BlueGene/L

Hi all, when trying to build LLVM+Clang (r180247) on a BlueGene/Q, I get the following error message (multiple times): llvm[3]: Building PPC.td code emitter with tblgen llvm-tblgen: Unknown command line argument '-gen-emitter'. Try: '/homea/jjsc13/jjsc1301/.pool/.build/llvm_r180241/Release+Asserts/bin/llvm-tblgen -help' llvm-tblgen: Did you mean '-mc-emitter'? Has

Hello, Koen. > So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 > to ARM/EABI? Well, just supply appropriate --host/--target options to configure. I haven't tried ARM, but this definitely works for crosscompiling from linux to mingw32. Please also note, that you'll need native (=arm) tools (binutils, libcheaders, etc) during gcc build

2011/4/8 ether zhhb <etherzhhb at gmail.com>: > Hi, > > 2011/4/8 Vlad Krylov <krvladislav at gmail.com>: >> Hi. >> >> I see that to detect scops firstly we search for regions in CFG ( by >> RegionInfo ) and then select regions that answer some requirements ( >> in ScopDetection ). Because only affine expressions in conditions and >> bounds

Hi, While crosscompiling the kernel for openrisc with allmodconfig the build failed with the error: drivers/vhost/vhost.c: In function 'vhost_vring_ioctl': drivers/vhost/vhost.c:818:3: error: call to '__compiletime_assert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE Can you please give me any idea about what the

Hi, While crosscompiling the kernel for openrisc with allmodconfig the build failed with the error: drivers/vhost/vhost.c: In function 'vhost_vring_ioctl': drivers/vhost/vhost.c:818:3: error: call to '__compiletime_assert_818' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE Can you please give me any idea about what the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Korobeynikov schreef: > Hello, Koen. > >> So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 >> to ARM/EABI? > Well, just supply appropriate --host/--target options to configure. To llvm or llvm-gcc4? > I haven't tried ARM, but this definitely works for crosscompiling from

On 04/08/2011 08:35 PM, Vlad Krylov wrote: > 2011/4/8 ether zhhb<etherzhhb at gmail.com>: >> Hi, >> >> 2011/4/8 Vlad Krylov<krvladislav at gmail.com>: >>> Hi. >>> >>> I see that to detect scops firstly we search for regions in CFG ( by >>> RegionInfo ) and then select regions that answer some requirements ( >>> in

Hi all! I want to cross compile openssh to our own CPU and our embedded Linux platform, however I get at least the following errors when running configure: checking whether snprintf correctly terminates long strings... configure: error: can not run test program while cross compiling checking whether getpgrp takes no argument... configure: error: cannot check getpgrp if cross compiling checking

http://bugs.winehq.org/show_bug.cgi?id=26614

Hi everyone, Colleagues of mine at Lawrence Livermore National Laboratory (LLNL), having seen the advantages of working closely with LLVM, have decided to toss their hat into the ring and would like to hire an LLVM-focused compiler engineer. I collaborate with LLNL regularly, and I'm excited that they're taking this step. I expect that a qualified applicant will find this position both

Hi Does anyone have experience of running CentOS on HP hardware, both rack mount kit and blades? How are things like hardware monitoring etc? We may be moving from Dell to HP and i get on really well with OMSA and Nagios etc so ideally would like to monitor using similar tools rather than some central 'enterprise' dashboard etc. Any real world experience? thanks

Dear All, I am actually on R-devel using shell consol. When I run RStudio, it can't find libR.so in the new /lib folder where is libRblas.so libRlapack.so. At first step I configure R-devel to share library with ./configure --enable-R-shlib. when I copied libR.so from /usr/lib/R/lib/libR.so (stable version R 3.1) to /usr/local/R-devel/lib/libR.so (R-devel version), That doesn't work.

libR seems to include a main() function. Should it? I'm hoping this simpler question will get more of a response than my previous post about R a la carte :) The evidence that libR includes main() is two-fold. First, when I use nm, I see the _main defined. Second, when I run a program linked to libR, the main R shell takes over, even though I have my own main (in another library). Looking

Hi, I forgot tools/rsync-recommended before ./configure Thanks On Mon, Mar 9, 2015 at 6:51 PM, Kevin Ushey <kevinushey at gmail.com> wrote: > I believe you need to set the environment variable R_HOME_DIR to the > path pointing to your R-devel installation before launching RStudio. > > On Mon, Mar 9, 2015 at 9:49 AM, Karim Mezhoud <kmezhoud at gmail.com> wrote: >

I have successfully installed Rserv (http://stats.math.uni-augsburg.de/Rserve) on Mac OS, but I have trouble on two different linux platforms. R CMD INSTALL Rserve_0.3-10.tar.gz fails with this message ** libs gcc -g -O2 -I/usr/local/include -L/usr/local/lib Rserv.c -o Rserve \ -DDAEMON -O -I/usr/local/lib/R/include -Iinclude -I. -lR -L/usr/local/lib/R/bin -ldl -lcrypt

Hi, I installed R 2.9.0 a couple of days ago on a linux machine. At the root of installation, I see 4 directories: bin, lib64, share, and src. I don't see libR.so anywhere. (In the following context, . (dot) indicates the root of my insta- llation.) I do see: ./lib64/R/lib/libRblas.so ./lib64/R/lib/libRlapack.so I became aware of such as I was preparing for an installation of little r.

Hi While installing RPy2, I had curious problems which, if I traced them back correctly, have their root in the way that libR.so find the R installation directory. I wonder if this might be a subtle bug that only causes problems when one has several versions of R on one system but then can be very annoying and cause very strange behaviour. It seems to me that libR.so asks the Unix shell to

It doen't seem to be anyting seriuos but I get this when crosscompiling not otherwise. <p><p> from ../../src/bitstream/bitstream.c:57: ../../src/bitstream/../portab.h:61: warning: `ARCH_IS_32BIT' redefined *Initialization*:1: warning: this is the location of the previous definition <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg

I have the problem that configure can't run the binaries, due to crosscompiling. How can you solve these issues with ./configure? checking whether size_t is signed... configure: error: cannot run test program while cross compiling See `config.log' for more details. I configure with a mipsel cross compiler. Cheers Martin

Hello Philipp, > Does that mean that I will have to configure llvm as a cross-compiler > even when using the C backend? Not llvm, but llvm-gcc only. I've successfully used llvm-gcc for crosscompiling with host=linux and target=mingw32 platform. So, you have just to supply host, build and target triples to llvm-gcc configure and be also sure, that configure will find target headers,