similar to: Errors compiling wine under Red Hat

I tested also with a clean git source. Something wrong with ole32. Code: -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wstrict-prototypes -Wtype-limits -Wwrite-strings -fno-omit-frame-pointer -Wpointer-arith -Wlogical-op -I/usr/include/freetype2 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o tmarshal_i.o tmarshal_i.c

When I try to build wine 1.1.15 in Fedora 8 I get this error > sh: i686-redhat-linux-gnu-as: command not found > winebuild: i686-redhat-linux-gnu-as failed with status 32512 > winegcc: ../../tools/winebuild/winebuild failed > make[2]: *** [acledit.dll.so] Error 2 > make[2]: Leaving directory `/home/user/rpmbuild/BUILD/wine-1.1.15/dlls/acledit' > make[1]: *** [acledit] Error

What are the advantages of using winegcc over the mingw cross compiler? Also, what are the differences in the header files / libs supplied with each ? I have an app (http://www.autohotkey.com/forum/viewtopic.php?t=46546) cross compiling with mingw using codeblocks, and I have it working under winelib side by side native linux code. I wanted to translate it so it would compile with winegcc so

yes, winegcc generates x86 output. I ever conpiled it on a non-x86 box. I did not remember whether the generated winegcc generated native code or x86 code. e.g, how winegcc generates powerpc code.

Hello! Problem with winegcc. Could you please write me where is my mistake? t:~$ LANG=C make pc winegcc -o inkdemo.pc src/*.c -linkview -lfreetype -ljpeg -lz /usr/local/lib/libinkview.a(hw_emulator.o): In function `eink_waveform': hw_emulator.c:(.text+0xa22): undefined reference to `SetBitmapBits' hw_emulator.c:(.text+0xa73): undefined reference to `BitBlt'

Hi!! I am not able to compile a test program on solaris using winegcc tool. Can anybody help? Here's the program source code: // file test.cpp #include <stdio.h> #include <windows.h> int main () { SYSTEMTIME lpSystemTime; GetSystemTime(&lpSystemTime); printf("Today is: %d/%d/%d\n", lpSystemTime.wYear,

Hi, I have Mandriva 2006 x86_64. I tried to install wine, but the binaries are for 32 bits and the result is very instable (win programs close suddenly, no internet available for those programs, etc...) So I tried to compile wine 0.9.14 from source, but I have an error during make when "searching for -lXext" : LD_LIBRARY_PATH="../../libs/unicode:$LD_LIBRARY_PATH"

Hi ! After download latest version from cvs compile fails: make[2]: Entering directory `/backup/privat/emulator/wine/dlls/activeds' gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o activeds_main.o activeds_main.c ../../tools/winebuild/winebuild -D__WINESRC__

Hi all, I am trying to build wine-20040309, and i am facing a gcc crash while compiling winetest. The log is below (sorry : it's localized in french). make[2]: Entre dans le r?pertoire `/home/root/build/wine-20040309/programs/winetest'../../tools/winegcc/winegcc -B../../tools/winebuild -mwindows gui.o main.o send.o util.o winetest.exe.dbg.o gui.res winetest.res -o winetest.exe.so

When compiling in Ubuntu 6.06 64 bit using this guide: http://wiki.winehq.org/WineOn64bit When I do 'sudo make install' I get this error: make[2]: Entering directory `/home/marcus/wine/dlls/gdi' ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./gdi32.spec dispdib.spec.o gdi.exe.spec.o wing.spec.o bidi16.o dispdib.o env.o gdi16.o metafile16.o wing.o bidi.o bitblt.o

I installed 1.1.6 and it was working fine except for one application. I installed 0.9.32 after changing my .wine directory to .wine_bak. (someone mentioned that they had got my application to work on the older version). The application still didn't work, so I changed my .wine directory to .wine932, and changed my .wine_bak to .wine. At that point I expected everything to be back to where I had

I'm trying to compile ver 20041019 (older ver for winetools) on my x86_64 Fedora Core 3. ./configure works fine, and so does make depend, but when it comes down to actually compiling, it has a hard time locating the right libs to link against. ../../../tools/winegcc/winegcc -B../../../tools/winebuild -shared ./winearts.drv.spec arts.o audio.o winearts.drv.dbg.o -o winearts.drv.so

I failed to link a .so built with g++ to wine. winegcc can not link g++ .o files to .so file. how can I use c++ with wine?

Here is how I compiled 0.9.13: #!/bin/bash # note that the following is all one bash line CFLAGS="-L/emul/linux/x86/usr/lib -L/emul/linux/x86/lib"\ LDFLAGS="-L/emul/linux/x86/usr/lib -L/emul/linux/x86/lib" \ ./configure --x-libraries=/emul/linux/x86/usr/lib/ && make depend all I tried the same with 0.9.14 but it failed like this: ../../tools/winegcc/winegcc

I cant build the new crypt32 tests added by Kees Cook with the latest CVS. I actually get undefined references to CryptUnprotectData : [syl@wine tests]$ make ../../../tools/winegcc/winegcc -B../../../tools/winebuild -mconsole protectdata.o testlist.o -o crypt32_test.exe.so -L../../../libs/port -lwine_port -L../../../dlls -L../../../dlls/crypt32 -L../../../libs -lcrypt32

I eventually want to write a Linux application that can load Windows DLLs using winelib (I can do that, right?) but to start off, I just wanted to do a little Hello World test. Here's what I've got: main.c Code: #include <windows.h> int main(int argc, char** argv) { MessageBox(NULL, "Hello world.", "Hello", MB_OK); return 0; } This compiles fine

hello all, cannot compile wine Version 0.9.2 under suse10-x86_64, neither from source nor from the src-rpm. there must be some trouble between libraries: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ddraw.spec clip per.o ddraw_hal.o ddraw_main.o ddraw_thunks.o ddraw_user.o ddraw_utils.o main.o palette_hal.o palette_main.o regsvr.o surface_dib.o surface_fakezbuffer.o surfac

Suppose that I have Windows application using Code: LoadLibrary followed by Code: GetProcAddress It should be possible to load a library implemented in terms of POSIX function but I do not understand how. Should I load the dll.so file generated by winegcc or do i need a plain .dll file?[/code]

I'm on Linux Mint Fluxbox CE 5 trying to compile the latest Git source. I previously had Wine 1.0 something from the Synaptic repos, and wanted bleeding edge so I did Code: $ aptitude remove wine and then followed the Wine + Git instructions. After the repo was cloned I ran ./configure, installed a couple dependencies and libfreetype-dev, and the config script then ran fine. Then I

Greetings All, I am attempting to compile wine under the SUSE 10.2 64 bit distribution, and am running into a bit of a problem. I have installed every 32 bit library that I could find in the distro, including the xorg-X11 libs. I ran the following commands: ./configure --prefix=/usr --x-libraries=/usr/X11R6/lib make depend && make The compilation chugs away for about 15 min,