On Thu, 3 Jun 2004 15:37:19 +0200, Maurizio Monge wrote:
> Hello, i have retried to compile wine CVS on amd64 (gcc 3.4 with -m32, etc +
> kernel 2.6.4-rc2), where i was thinking the 0xc000 problem was solved.
> but i get:
Hmm, wine 20040505 works on my AMD64 system (using a biarch 2.6.6 kern
> Maurizio,
> Ignore what it says in the source, in dlls/ntdlls/virtual.c you can change
> the value in ADDRESS_SPACE_LIMIT to suit yourself. Many applications (I
> venture to say most ) work fine and my solaris distro has been compiled
> like this for two years with few (Actually no) complai
On Sat, 5 Jun 2004 04:14 am, Alexandre Julliard wrote:
> Maurizio Monge <[EMAIL PROTECTED]> writes:
> > # wine-kthread
> > wine: failed to initialize: /opt/wine/lib/wine/ntdll.dll.so: failed to
> > map segment from shared object: Cannot allocate memory
>
> Sounds like the kernel will need to be fix
Maurizio Monge <[EMAIL PROTECTED]> writes:
> # wine-kthread
> wine: failed to initialize: /opt/wine/lib/wine/ntdll.dll.so: failed to map
> segment from shared object: Cannot allocate memory
Sounds like the kernel will need to be fixed. If there's no way to map
dlls below 0x8000 many things w
Alle Friday 04 June 2004 01:34, Alexandre Julliard ha scritto:
> wine-kthread
# wine-kthread
wine: failed to initialize: /opt/wine/lib/wine/ntdll.dll.so: failed to map
segment from shared object: Cannot allocate memory
:-(
Maurizio
CC to monge(at)sns(dot)it
Maurizio Monge <[EMAIL PROTECTED]> writes:
> old_mmap(NULL, 482376, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = -1 ENOMEM
>
> (Cannot allocate memory)
>
> It looks like my kernel absolutly wants to allocate memory > 0xc000 :-)
>
Hello, i have retried to compile wine CVS on amd64 (gcc 3.4 with -m32, etc +
kernel 2.6.4-rc2), where i was thinking the 0xc000 problem was solved.
but i get:
wine: failed to initialize: /opt/wine/lib/wine/ntdll.dll.so: failed to map
segment from shared object: Cannot allocate memory
attac
