similar to: Problems building dlls for use with winelib

I am doing some testing with WineLib and the 20010731 release and am having some trouble with the final linkage. I have a very simple test.cpp file and the following spec file: name test mode guiexe type win32 import shell32.dll import comdlg32.dll import user32.dll import gdi32.dll import kernel32.dll import ntdll.dll and a hand crafted make file. When I run the make I get the

Dear all, I have the following data structure > print(testlib) $tags tag count.raw count.adj err 1 aaaaaaaaaa 94 93 0.5 2 aaaaaaaaac 1 2 0.2 3 aaaaaaaaag 3 2 0.1 4 aaaaaaaaca 1 1 0.003 I want to iterate the data above and print

Hi, I have the following problem - when I compile a DLL using winegcc and call GetModuleFileName on it I get a name in "c:\windows\system", regardless of the DLLs actual location. I have googled for it, and found this thread http://www.winehq.org/pipermail/wine-devel/2003-December/023224.html which says that this behavior is needed for built-in DLLs. My problem is that I'm

Do I need to do anything special to access classes in RAILS_ROOT/lib from a worker? Maybe: require File.dirname(__FILE__) + ''../my_lib.rb'' or does it do that automatically like a controller does? Also if I write a unit test for a worker that is accessing AR, is there anything special needed to be done to access fixtures etc to test it? Thanks -- Jim Morris,

Hi, I try to port a Windows-console application to Linux. I did this: > winemaker --lower-uppercase --console -I/usr/include/wine -L/usr/include/wine . > ./configure > make Now all object files are created without warnings or errors, but while linking this error is printed out: [....] LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/bin/winebuild -fPIC -o koordkonsole2.exe.spec.c

I encountered a new build failure (r227128) on my nightly build of LLVM for MinGW: FAILED: cmd.exe /c cd . && D:\MinGW\x86_64-4.9.1-release-posix-seh-rt_v3-rev0\mingw64\bin\c++.exe -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wno-comment -std=gnu++11 -g

\tools\clang\tools\CIndex && D:\Tools\Building\cmake\bin\cmake.exe -E cmake_link_script CMakeFiles\CIndex.dir\link.txt --verbose=1 D:\Tools\Building\gcc\bin\g++.exe -shared -o ..\..\..\..\bin\libCIndex.dll -Wl,--out-implib,..\..\..\..\lib\libCIndex.dll.a -Wl,--major-image-version,0,--minor-image-version,0 CMakeFiles\CIndex.dir\CIndex.cpp.obj ..\..\..\..\lib\libLLVMMC.a

CentOS 6 has libguestfs-devel 1.20.11, which predates the support in guestfs_add_drive_opts() for requesting an nbd drive instead of a local file (annoyingly, guestfs documentation merely states the function was available since 0.3, without saying which later releases added new options); causing a compilation failure during 'make check'. Maybe the guestfs plugin should still be built,

Some additional information about the setup may be of interest: I'm using CMake to generate the make files for MSYS. All appears to go well until the tools are compiled. The undefined references seem to be coming from the libraries that were just compiled: ../../lib/libLLVMBitReader.a(BitcodeReader.cpp.obj):fake:(.rdata$linkonce_ZTVN4llvm8ConstantE+0x10): undefined reference to

Hey Guys, I'm working on a project in Android related to System-level Audio DSP Effects for Tuning Android Audio. I want to leverage Faust ( https://faust.grame.fr/) to allow users to program their own filters. Faust provides a libfaust implementation which includes a JIT Compiler which leverages LLVM and seems to be the best path for me to use. Unfortunately I'm having problems

Just downloaded the latest release 2.2.30.2, ran ./configure with all defaults and make ... and it fails to build .. error somewhere whilst running Makefile in lib-http libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -Wl,--as-needed -o

Is fPIC broken on x86_64 in LLVM 2.6? I looked through the release notes but did not see anything mentioned. When I try: ------------------- > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc file.c > llvm-ld -native -Xlinker=-shared -Xlinker=-Wl,-soname,libtest.so -o file.so file.opt.bc ------------------- on an x86 machine it works fine. When I try it on x86_64, the

On 28.03.2018 22:14, Odhiambo Washington wrote: > > > On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > Hi! > > We are releasing v2.3.1, which mostly consists of bug fixes for > 2.3.0, and few improvements. This is also available via > https://repo.dovecot.org if you want packages. libsodium

On 29.03.2018 10:36, Odhiambo Washington wrote: > > > On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> On 27 March 2018 at 20:06, <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at dovecot.fi>>

On 29.03.2018 13:14, Odhiambo Washington wrote: > > > On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi > <mailto:aki.tuomi at dovecot.fi>> wrote: > > > > On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at

Hi! We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, and few improvements. This is also available via https://repo.dovecot.org if you want packages. libsodium support didn't get into this build, due to build environment issues, but 2.3.2 will contain it. * Submission server support improvements and bug fixes - Lots of bug fixes to submission server * API CHANGE:

Hi! We are releasing v2.3.1, which mostly consists of bug fixes for 2.3.0, and few improvements. This is also available via https://repo.dovecot.org if you want packages. libsodium support didn't get into this build, due to build environment issues, but 2.3.2 will contain it. * Submission server support improvements and bug fixes - Lots of bug fixes to submission server * API CHANGE:

Hi Ashi, Your first LDR is a pseudoinstruction that is supported by some tools (gas and armasm, at least), but not by LLVM. Roughly speaking, it turns into a PC-relative load from a literal pool. To do what you're trying to achieve you can write your own literal pool in your assembly. You can see some examples of this sort of thing at

On Tue, Jan 27, 2015 at 10:02 AM, Mueller-Roemer, Johannes Sebastian <Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote: > Adding -D__MSVCRT_VERSION__=0x900 (or higher) to CMAKE_CXX_FLAGS and > -lmsvcr90 (or higher) to CMAKE_CXX_STANDARD_LIBRARIES appears to work. > -lmsvcrt80 does not work, contrary to the comment on the MinGW bug tracker. > However, if you do not

Trying to build Dovecot 2.2.34 on OpenBSD fails. This seems to have been introduced by this commit.. https://github.com/dovecot/core/commit/4a9020ed888caf03fd3132a30a7818b01daa4b9d Fairly -current.. /usr/bin/libtool --tag=CC --mode=link cc -std=gnu99 -O2 -pipe -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast