Hi Rob!
>
> There are quite a few places that use i386 syscalls directly and you
> just fixed the one place it was detected. What you need to do is to copy
> a 32-bit unistd.h to asm-i386/unistd.h and make sure that it is included
> correctly by asm/unistd.h.
>
Many thanks for your explanati
Pavel Troller wrote:
Hi!
I would like to ask for a help with wine compilation on an x86_64 system.
Today I successfully did the compilation, but the result is totally unusable.
I've supplied -m32 switch to both CFLAGS and LDFLAGS (I have to specify my
own C/LDFLAGS because of custom -I/-L opt
Pavel Troller wrote:
> I would like to ask for a help with wine compilation on an x86_64 system.
http://wiki.winehq.org/WineOn64bit
bye
michael
> Today I successfully did the compilation, but the result is totally
> unusable.
> I've supplied -m32 switch to both CFLAGS and LDFLAGS (
Hi Pavel,
One thing to consider is where gcc finds your X libraries. Wine knows its on
a x86_64 system and supplies the -m32 itself. Of course, you will have to
watch out for missing required packages reported by configure (bison, flex
libxml2-devel, libxslt-devel, cups-devel, fontforge, freetype2
Hi!
I would like to ask for a help with wine compilation on an x86_64 system.
Today I successfully did the compilation, but the result is totally unusable.
I've supplied -m32 switch to both CFLAGS and LDFLAGS (I have to specify my
own C/LDFLAGS because of custom -I/-L options to find various
