Re: Wine on FreeBSD current

2004-10-31 Thread Gerald Pfeifer
On Tue, 22 Jun 2004, Alexandre Julliard wrote: Gerald Pfeifer <[EMAIL PROTECTED]> writes: ...and in fact, Alexandre, wouldn't it be better to have _some_ apps broken under Wine on FreeBSD than a completely broken Wine on FreeBSD for all apps? Nope. What matters is not so much how many apps run to

Re: Wine on FreeBSD current

2004-06-23 Thread Gerald Pfeifer
On Mon, 21 Jun 2004, John Birrell wrote: > For FreeBSD5, which will become the stable branch sometime soon, I think > the kernel code needs to change. I have a FreeBSD src commit bit, but I'm not > a vm person, so I can only prototype a change and submit it for review. Excellent, thanks! Would yo

Re: Wine on FreeBSD current

2004-06-22 Thread Alexandre Julliard
Gerald Pfeifer <[EMAIL PROTECTED]> writes: > ...and in fact, Alexandre, wouldn't it be better to have _some_ apps > broken under Wine on FreeBSD than a completely broken Wine on FreeBSD > for all apps? Nope. What matters is not so much how many apps run today, but that we have a design that will

Re: Wine on FreeBSD current

2004-06-22 Thread John Birrell
On Tue, Jun 22, 2004 at 11:36:16PM +0200, Gerald Pfeifer wrote: > On Sun, 20 Jun 2004, Alexandre Julliard wrote: > > Well, there's a reason for that reservation code, and it's that some > > Windows apps require it; so unless you find some other way to ensure > > that FreeBSD never allocates anythin

Re: Wine on FreeBSD current

2004-06-20 Thread Alexandre Julliard
John Birrell <[EMAIL PROTECTED]> writes: > To get Wine to work on FreeBSD4, there needs to be a way of making the > reservation code optional. A simple mmap test in configure which snaffles > memory above 0x8000 and then tries to mmap some more memory without > specifying a fixed address would

Re: Wine on FreeBSD current

2004-06-20 Thread John Birrell
On Sun, Jun 20, 2004 at 04:57:43PM +0200, Gerald Pfeifer wrote: > On Thu, 17 Jun 2004, John Birrell wrote: > > "wine: failed to initialize: /something/lib/wine/ntdll.dll.so: mmap of > > entire address space failed: Cannot allocate memory" > > > > is caused by Wine attempting to mmap memory outside

Re: Wine on FreeBSD current

2004-06-20 Thread Gerald Pfeifer
On Thu, 17 Jun 2004, John Birrell wrote: > "wine: failed to initialize: /something/lib/wine/ntdll.dll.so: mmap of > entire address space failed: Cannot allocate memory" > > is caused by Wine attempting to mmap memory outside the user process > address space. I see mmap addr around 0xd810 (mostl

Re: Wine on FreeBSD current

2004-06-17 Thread Gerald Pfeifer
>> I'm just wondering if it is supposed to work as well as FreeBSD stable. Right now, Wine doesn't work at all on FreeBSD -STABLE: wine: failed to initialize: /swtest/wine/dlls/ntdll.dll.so: mmap of entire address space failed: Cannot allocate memory and before that I used to see deadlocks u

Re: Wine on FreeBSD current

2004-06-17 Thread Gerald Pfeifer
On Wed, 16 Jun 2004, Jonathan Fosburgh wrote: >> wine: failed to initialize: /swtest/wine/dlls/ntdll.dll.so: mmap of >> entire address space failed: Cannot allocate memory > I get the same problem on -CURRENT with recent CVS versions of wine. > Hopefully, in the port of the new release, this wi

Re: Wine on FreeBSD current

2004-06-17 Thread Mike Hearn
On Wed, 16 Jun 2004 13:54:37 -0500, Jonathan Fosburgh wrote: > I tried to look through the mmap.c code but I don't have enough of an > understanding of what it is supposed to do to figure out how to make it work, > or even work around it. It provides mmap emulation for some systems and is respon

Re: Wine on FreeBSD current

2004-06-17 Thread Jonathan Fosburgh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 June 2004 22:52, John Birrell wrote: > > Thanks for the reply. > > From what I can see, there are two problems with the Wine build from CVS > on FreeBSD -current that seem to be related to the use of BSD make. In the > dlls 'setupapi'

Re: Wine on FreeBSD current

2004-06-16 Thread John Birrell
On Wed, Jun 16, 2004 at 07:49:26PM +0200, Gerald Pfeifer wrote: > >> I'm just wondering if it is supposed to work as well as FreeBSD stable. > > Right now, Wine doesn't work at all on FreeBSD -STABLE: > > wine: failed to initialize: /swtest/wine/dlls/ntdll.dll.so: mmap of > entire address spa

Re: Wine on FreeBSD current

2004-06-16 Thread Jonathan Fosburgh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 June 2004 13:19, Gerald Pfeifer wrote: > > Given that I'm the maintainer of the wine port in FreeBSD, I can say > quite authoritatively that I probably won't update to the latest snapshot, > unless some third party is able to provide a

Re: Wine on FreeBSD current

2004-06-16 Thread Jonathan Fosburgh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 June 2004 12:49, Gerald Pfeifer wrote: > >> I'm just wondering if it is supposed to work as well as FreeBSD stable. > > Right now, Wine doesn't work at all on FreeBSD -STABLE: > > wine: failed to initialize: /swtest/wine/dlls/ntdll.dl

Re: Wine on FreeBSD current

2004-06-09 Thread Jonathan Fosburgh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 09 June 2004 01:42, John Birrell wrote: > Are there any people subscribed to this list who use Wine on FreeBSD > current? > > I'm just wondering if it is supposed to work as well as FreeBSD stable. There is a threading problem right now (s