search for: dynamiclibrari

Reid, I'm just curious to know if these errors are on your new year list :) ---------------- make[1]: Entering directory `/C/projects/build/MinGW/llvm-1-1/lib/System' llvm[1]: Compiling DynamicLibrary.cpp for Debug build In file included from c:/projects/src/llvm-1/llvm/lib/System/DynamicLibrary.cpp:25: c:/projects/src/llvm-1/llvm/lib/System/win32/DynamicLibrary.cpp:22: warning:

I'm trying to compile LLVM with musl libc library. The compilation process fails on the following: x86_64-linux-musl-g++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter

Not really. I'm pretty much leaving the win32 directory up to Jeff Cohen these days. I don't have a way to replicate the problem. Reid. On Wed, 2004-12-29 at 12:46, Henrik Bach wrote: > Reid, > > I'm just curious to know if these errors are on your new year list :) > ---------------- > make[1]: Entering directory `/C/projects/build/MinGW/llvm-1-1/lib/System' >

I have no way of duplicating mingw problems either, but in this case the fix is obvious and has been committed. Reid Spencer wrote: >Not really. I'm pretty much leaving the win32 directory up to Jeff Cohen >these days. I don't have a way to replicate the problem. > >Reid. > >On Wed, 2004-12-29 at 12:46, Henrik Bach wrote: > > >>Reid, >>

Hi, Has anyone succeeded in building llvm on AIX? Currently I am investigating several tools for code analyses and I came upon Clang. We at CCV run our core business applications on RS6000/AIX. At our department we develop those applications. The reviews on clang look very promising. I was able to build and run it on Linux (SuSE 12.1) without any problems. I tested it with valgrind sources and

The interpreter still resolves printf using a hack. It does try to use DynamicLibrary to find it, but fails. DynamicLibrary on Windows only searches the main program executable for symbols, lli.exe in this case. As the C/C++ runtime is in a DLL, it won't find printf in lli.exe. It ought to then search the runtime DLL, the name of which depends on how the binaries are built, but it

Misha, The "equivalent of dlsym" should be working just fine. Its called ltdl (libtool dynamic library) and is part of lib/System. Its interface is the DynamicLibrary class. The interpreter has already been modified to use this facility. So, if this is broken on windows, I'd like to know how, or why. Jeff, can you provide a test case that we can use to reproduce this problem?

I use the one from mingw.org, installed by the recommended way with mingw-get-setup.exe. Sly. On 30.08.2015 06:10, Yaron Keren wrote: > Which mingw distribution exactly do you use? > > 2015-08-30 0:46 GMT+03:00 Slycelote via llvm-dev <llvm-dev at lists.llvm.org>: > >> Hi all, >> >> I'm hitting the same problem as in this[1] thread. I use release_37

Hi all, I'm hitting the same problem as in this[1] thread. I use release_37 branch on 64-bit Windows 7. The problem is here: #ifdef __MINGW32__ #include <imagehlp.h> #else #include <dbghelp.h> #endif <skip> typedef BOOL (WINAPI *fpEnumerateLoadedModules)(HANDLE,PENUMLOADED_MODULES_CALLBACK64,PVOID); imagehlp.h doesn't define PENUMLOADED_MODULES_CALLBACK64 type. I

I don't know since when, but this file has been changed to remove all the trickery (aka defines) needed for MinGW-w64 (and probably everything else that as forgotten) to succesfully compile it. Attached is a patch that reintroduces the compiler checking. I would like to see this in LLVM 3.0, otherwise (by the looks of the reintroduced code) anything newer than _MSC_VER_1500 will be broken.

There's a problem with the license for ltdl.c when building with VC++. It is under the LGPL, with a special exception: As a special exception to the GNU Lesser General Public License, if you distribute this file as part of a program or library that is built using GNU libtool, you may include it under the same distribution terms that you use for the rest of that program. The problem is,

I'm using llvm::sys::DynamicLibrary to export Symbols from my host-application to a JIT instance. Now I was wondering what the scope of this DynamicLibrary is, because I think I never attached it to the JIT or the module. Would it be possible to use the exported symbols even from a separate process (e.g. a forked off JIT), as long as the host app is running? -Frank

Hi, I tried building LLVM with the downloaded sources. I am building it with gcc4.3. After getting configured successfully, and running 'make', build fails with the following message: make[1]: Entering directory `/home/guest/SRC/llvm-2.1/lib/System' llvm[1]: Compiling DynamicLibrary.cpp for Release build DynamicLibrary.cpp: In static member function âstatic void*

Hi everybody, I just updated to the latest svn trunk version, but now the code does not compile anymore. It trows an error in "f:\dev\llvm\lib\system\Win32/DynamicLibrary.inc(159) : error C2228: left of '.find' must have class/struct/union". Below you can find the small patch which makes the compiler happy again :-) Sincerely yours Marius Wachtler

Hello, Alain. > I'm starting to play with LLVM today and I've trouble compiling it. > I'm > working under Windows Vista, with the gcc from Cygwin: Oh, this seems to be killer mix :) GCC (at least native mingw32 port) has known problems being running on Vista. > Is LLVM supposed to work with this version of GCC (probably using the > -mno-cygwin option to get a

On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > Nick, > I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative > as the dyld error occurs right after... > > (gdb) > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at

Hello there, I'm having a problem compiling llvm with vc++ 2005 and windows sdk6.1. It seems that the Platform SDK supplied with vc++2005 uses PSTR for the first param of PENUMLOADED_MODULES_CALLBACK64 typedef (dbghelp.h) and the windows sdk 6.1 (also windows sdk 6.0a that ships with vc++2008) uses PCSTR. The _MSC_VER macro guard for ELM_Callback(...) kinda kills the possibility of using

Hi, We need to support unloading of shared libraries. I'd like to continue using sys::DynamicLibrary. Few questions: * Is there a fundamental reason not to implement UnloadLibrary? * Would it be necessary to implement some fancy symbol use-check for unloading, or would it be fine to make this a "use at your own risk" operation? At least as a first implementation? * I would also

Hi, Attached patch moves code around; it should not have a functional effect. It formalizes a few concepts that were spread over several files before, depending on platform. It removes historical leftovers. Symbol lookup now happens in three easy phases, on all platforms: * explicitly provided symbols through AddSymbol() * shared libraries * platform provided "special" symbols. No

I tried to build the latest using Visual Studio and ran into a few problems. Patches attached to fix most of them. However, there's one I can't easily fix. DynamicLibrary.cpp is messed up. lib/System/DynamicLibrary.cpp does NOT include platform/DynamicLibrary.cpp like it's supposed to, so the Windows-specific implementation is not compiled. What's there now is very