similar to: [LLVMdev] --enable-shared doesn't build shared library any more

Yuri, on which host? 2011/8/17 Yuri <yuri at rawbw.com>: > In r134967 it still worked, and in r137742 it now doesn't. > I used such flags: --enable-assertions --enable-shared --enable-libffi > --enable-debug-runtime --enable-debug-symbols --disable-optimized > > Before build would create directory tools/llvm-shlib under the build > tree. Now it is missing. In my

Hi, I directed somebody to install R (2.6.1) on his OSX computer, following instructions from http://cran.r-project.org/bin/macosx. She can run R from the console. But plot(1:10) doesn't produce any output or open a window (as I am used to from linux). More importantly: Rscript is not in the path (minor problem ln -s is hopefully doable). I tried to put a hardcoded path to Rscript into the

How about building this in the CMake or auto* level we build a separate build script for it? I attache a simple version here. It does seem to work here. It's a shell script, which uses cmake for the building but it seems the second stage file works. I am not really sure why a third stage is needed, but it can be added quite easily. A windows version should be trivial to write (next week). A

There's functionality in the make build to update (at least one layer of) nested svn working copies of LLVM, but nothing in cmake and nothing for git in either. I use the following script & after updating it to handle arbitrary nesting (with the advent of the clang-tools-extra repository) & generalize the discovery (had a hardcoded list & after fixing up the Make build after some

> We want to make Clang great, and we need your help! Doug, I don't see any type of selfbuild target in the LLVM top level makefile. This would be a useful way to automate the self build process. I've used similar mechanisms before on other compilers, where you can trivially invoke a three phase build (first you do a full build with your system compiler, then you use your built

> But I don't think there's a reason we couldn't point the bots at the github > mirrors. I'm not sure if they lag the official mirror though. The GitHub mirrors located at [1] are updated hourly which is not frequent enough There seems to be an LLVM organisation registered on GitHub but it doesn't seem to be in use. [1] https://github.com/llvm-mirror/ [2]

opensuse 10/find / samba-3.0.20b-3.3 I'm trying to change directory permissions on a share so all users can modify files in the share and when I do as suggested in Ch15 of Samba Howto the following happens $ find `directory_name' -type d -exec chown nobody:users {}\; find: missing argument to `-exec' Chris Boyd Systems Engineer USIT 19-21 Aston Quay Dublin 2 Ireland Tel: +353 1

Hello fellow LLVMers and Clangstas, We want to make Clang great, and we need your help! Helping is easy: just build Clang on your platform and start using it as your main compiler for LLVM and Clang development. Much of the Clang team has been living on Clang for at least several weeks already, and we've found it to be quite stable for development. If you run into problems---poor

On 16 Aug 2019 at 5:40, Ady Ady via Syslinux wrote: To: "syslinux at zytor.com" <syslinux at zytor.com> Date sent: Fri, 16 Aug 2019 05:40:45 +0000 Subject: Re: [syslinux] Question on upgrading to syslinux 6.04? From: Ady Ady via Syslinux <syslinux at syslinux.org> Send reply to: Ady Ady <ady-sf at hotmail.com> > > I've

How about fitting Android's repo? :D I have not used repo for llvm, but been using my synthesized repository (for my buildbot). https://github.com/chapuni/llvm-project https://github.com/chapuni/llvm-project-submodule ...Takumi

Hi , This Is 'Suresh M' from AMD compiler team. 1) I obtained the source code of llvm and pool-alloc (relase_32 versions ) using the following commands, svn co http://llvm.org/svn/llvm-project/llvm/branches/release_32 llvm cd llvm/projects svn co http://llvm.org/svn/llvm-project/poolalloc/branches/release_32 poolalloc 2) Was able to build the binaries and libraries

Hello everyone, I'm trying to run a LLVM-Bytecode-file in the interpreter (lli --force-interpreter), but i'm getting the following error-message: LLVM ERROR: Tried to execute an unknown external function: i8* (i32)* malloc My program is calling malloc. If I omit --force-interpreter everything runs as expected. Compiling to Assembler also works without problems. I have compiled LLVM with

On 03/11/16 19:37, Volker Lendecke wrote: > On Thu, Nov 03, 2016 at 07:11:12PM +0000, Alex Crow via samba wrote: >> >> On 03/11/16 14:28, Ralph Böhme wrote: >>>> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man >>>> smb.conf" this should be set, but I don't remember seeing it on the wiki >>>> pages.

I am trying to build 2.7 on FreeBSD with all debugging options "on": CXX=/usr/local/gcc/4.5.0/bin/g++ CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ../llvm/configure --prefix=/usr/local/llvm/2.7 --enable-assertions --enable-shared --enable-libffi --enable-debug-runtime --enable-expensive-checks --enable-debug-symbols Here is the error message I got from the build:

It seems llvm interpreter only supports a limited number of external functions. fmod, in particular is not supported. any reason why it is not supported ? "lli -force-interpreter test.bc LLVM ERROR: Tried to execute an unknown external function: double (double, double)* fmod " -- Kind Regards Xin Tong -------------- next part -------------- An HTML attachment was scrubbed... URL:

Nick Lewycky <nicholas at mxc.ca> writes: > The interpreter uses libffi to make external function calls. However, it > needs to be detected at LLVM's compile time. If you're using the > released packages, we disabled that because we were worried about users > who don't have libffi installed. This seems to be quite a common problem (I too hit it once, thought it

On Thu, Nov 20, 2014 at 12:19:06AM +0100, Joerg Sonnenberger wrote: > On Wed, Nov 19, 2014 at 01:53:17PM -0800, Peter Collingbourne wrote: > > llgo depends on certain third-party components, namely a copy of the Go > > standard library (libgo), a Go program analysis library (go.tools) and two > > library dependencies of the standard library (libbacktrace and libffi). >

On 02/01/2010 01:13 PM, Kristaps Straupe wrote: > Hello again! > > We have fetched the latest llvm sources from repository and the > original problem has went away. Though now we are facing a new problem > with interpreter on the following c code: > > -------------- > #include <stdarg.h> > #include <stdio.h> > > void doTheThing(int dummy, ...) > {

I noticed that runFunction (for MCJIT) is very limited. At the same time the interpreter already has a fairly generic way of calling functions from a pointer and a Function * (for description) using libffi. Would it make sense to pull that functionality out into a small support library and using it in MCJIT? As is runFunction isn't particularly usable. -- Johannes S. Mueller-Roemer, MSc Wiss.

Hello again! We have fetched the latest llvm sources from repository and the original problem has went away. Though now we are facing a new problem with interpreter on the following c code: -------------- #include <stdarg.h> #include <stdio.h> void doTheThing(int dummy, ...) { va_list ap; int z; va_start(ap, dummy); while( (z = va_arg(ap, int))!=0) { printf("==