similar to: Building LLVM under Cygwin32 fails

Googling indicates that cygwin doesn't have that functionality. Or, at least, didn't in 2010, when someone asked about the same problem: https://cygwin.com/ml/cygwin/2010-01/msg00596.html "cygwin has only dlsym() not the SGI DL_info + dladdr() yet. clang just needs it to get the path for the CIndex dll. This should be possible with the code in the LLVM_ON_WIN32 section, and convert

I get the following problem building LLVM 2.7 on AIX 6: gmake[1]: Entering directory `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' llvm[1]: Compiling Path.cpp for Release build In file included from Path.cpp:262: Unix/Path.inc: In static member function 'static llvm::sys::Path llvm::sys::Path::GetTemporaryDirectory(std::string*)': Unix/Path.inc:142: error: 'mkdtemp' was

Dear Patrick, Documentation on some AIX routines to do the same thing can be found at http://publib.boulder.ibm.com/infocenter/comphelp/v8v101/index.jsp?topic=/com.ibm.xlcpp8a.doc/proguide/ref/dynamic_load.htm. Interestingly enough, the same page suggests that AIX does, in fact, support dlopen() and friends for POSIX compatibility. You might need to find out if there's a header file or a

On Aug 22, 2010, at 3:38 PM, Patrick Simmons wrote: > I get the following problem building LLVM 2.7 on AIX 6: > > gmake[1]: Entering directory > `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' > llvm[1]: Compiling Path.cpp for Release build > In file included from Path.cpp:262: > Unix/Path.inc: In static member function 'static llvm::sys::Path >

Not sure if this is me or not, because this is the first time I've built LLVM on Cygwin, but I can't get a working compile. I've configured with the following options: $ ./configure --with-llvmgccdir=/cygdrive/i/Projects/llvm-gcc4.2-2.2 --enable-debug-runtime --enable-jit --enable-targets=x86 Configure doesn't suggest there's anything wrong, but when I try make, I almost

Hi All, I am trying to build llvm on AIX. I installed all the required packages including gcc, g++, etc ./configure also went fine. but i tried to run gmake, i got the following error: llvm[1]: Compiling MemoryBuffer.cpp for Release+Asserts build llvm[1]: Compiling MemoryObject.cpp for Release+Asserts build llvm[1]: Compiling Mutex.cpp for Release+Asserts build llvm[1]: Compiling Path.cpp for

I've no idea, but without it, the 'std::to_string' definitions are not enabled! -----Original Message----- From: Renato Golin [mailto:renato.golin at linaro.org] Sent: 06 July 2016 19:35 To: Martin.ORiordan at movidius.com Cc: LLVM Developers <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] GCC prerequisites for building LLVM head? On 6 July 2016 at 19:02, Martin J.

Hi, Jules. On Tue, March 11, 2008 2:14 pm, Jules wrote: > Not sure if this is me or not, because this is the first time I've built > LLVM on Cygwin, but I can't get a working compile. Last I checked, LLVM-on-Cygwin has at least two problems, and you've hit one of them. Working around them isn't too bad, though patches to fix them would be appreciated. >

Seems like this in 83986 [1] needs a fix in Lapack.c: if (dladdr((void *) F77_NAME(ilaver), &dl_info)) { char buf[PATH_MAX+1]; char *res = realpath(dl_info.dli_fname, buf); if (res) { SEXP nfo = R_NilValue; if (strstr(res, "flexiblas")) nfo = R_flexiblas_info(); if

Hi everyone, I ran into a false positive with memory sanitizer due to it not intercepting dlinfo. I tried to get started on writing such an interceptor, but dlinfo seems like an extraordinarily difficult function to intercept. The three considerations that I would like somebody to look at are: 1) How do we get the enum values to decide what kind of pointer dlinfo is getting. Ideally we'd

Thanks! I'll try that. In order to avoid starting a new thread, let me ask you the next question. One of the shared libraries I load calls strtol and msan fails to intercept it. Why would this be? The library seems to be otherwise implemented. One of the potential culprits I saw is that strtol is marked as strong in libc. Is there any workaround? Keno On Thu, Apr 9, 2015 at 3:00 PM, Evgeniy

I am in the middle of the fun and games of updating my out-of-tree sources to the LLVM head revisions, and after updating to CMake v3.5.2 I am now getting a warning that 'ENABLE_TIMESTAMPS' is being ignored. Has support for embedding the timestamp in the build been removed or is there a new way of configuring it? I generally build internal transitional builds with this enabled so that

Hi, On Tue, Jun 28, 2016 at 3:25 PM, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I am in the middle of the fun and games of updating my out-of-tree sources > to the LLVM head revisions, and after updating to CMake v3.5.2 I am now > getting a warning that ‘ENABLE_TIMESTAMPS’ is being ignored. > > > > Has support for embedding the timestamp

I was able to process further by making some code changes and replacing export-dynamic with -bexpfull in Makefile.config. Now, i am getting following error while linking .. llvm[3]: Linking Release+Asserts Loadable Module LLVMHello.so ld: 0706-027 The -R $ORIGIN flag is ignored. ld: 0711-317 ERROR: Undefined symbol: llvm::Pass::getPassName() const ld: 0711-317 ERROR: Undefined symbol:

Hi, In FreeBSD 5.0-REL the dlinfo() manpage is present but the function does not seem to be implemented, is there a good reason for this ? -- Aurelien

On 12/7/16, Yaakov Selkowitz <yselkowitz at cygwin.com> wrote: > On 2016-12-07 17:57, Roger Pack wrote: >> Awesome. I tried building 3.9.0 today and ran into >> >> llvm-3.9.0.src/lib/Support/Unix/Signals.inc:418:5: error: ‘Dl_info’ >> was not declared in this scope >> Dl_info dlinfo; > > Already fixed upstream: > >

Hi. I''m considering an imminent switch from ext4 to btrfs and I''m hoping that someone can lend me advice before I do something unsupported. I have a software raid 6 array configured via mdadm. It was sitting at 8 x 3TB until I recently doubled that, grew the array and found that ext4 doesn''t want to resize. So, I''m looking to: 1. convert from ext4 to btrfs

Hello everyone! I seem to be have a bit of a problem setting up a few network folders for a my office on a Qnap storage device running Samba -v3.5.2. So I ask: when the 'write list' of a share contains ONLY groups, and a user tries to log on to that share, then samba authenticates against the primary group only of that user only?? Here is the example that fails: -the user is

hi, my old code compiles well on 3.1, but fails on 3.2. the compile error is like below. ... g++ -o vc main.o `llvm-config --libs all --ldflags` /usr/lib/libLLVMSupport.a(Signals.o): In function `PrintStackTrace(void*)': Signals.cpp:(.text+0x6c8): undefined reference to `dladdr' Signals.cpp:(.text+0x749): undefined reference to `dladdr' collect2: error: ld returned 1 exit status

ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a Solarisism. Luckily, getCurrentExecutablePath isn't being currently used anywhere in lli. ACTION: Wrap the method contents with #ifdef __sun__ ... #else return ""; #endif. If this functionality is actually desired, it would be more portable to hack up main() to join getcwd() with basename(argv[0]) to find the