On Sun, 20 Jun 2004 23:13:11 +0200, Ivan wrote:
> A user recently accidentally tried the Mandrake RPM on Red Hat and it wouldn't
> even run notepad.
> I build with no patches, no special stuff, just configure/make depend/make/make
> install
Yes, that's why we've written tools like apbuild, written
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
Lionel Ulmer <[EMAIL PROTECTED]> writes:
> So now we have two choices: either say 'well, this is a broken application,
> it does not run at all on modern Windows OSes' or add some special case when
> we set Wine's version to be 'win95' or 'win98' (a bit like we already do on
> instruction emulatio
Dan Kegel <[EMAIL PROTECTED]> writes:
> That failed immediately, so quickly that
>WINEDEBUG=+all wine wordpro.exe
> was practical to run. Here's part of its output. It looks as if
> the very first instruction accesses a null pointer in a strange
> way.
Most likely the dll was corrupted duri
> I've tried binary wine packages on a few occasions
> and *always* had major problems. Wine, and more importantly the things
A user recently accidentally tried the Mandrake RPM on Red Hat and it wouldn't
even run notepad.
I build with no patches, no special stuff, just configure/make depend/make
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
On Sat, Jun 19, 2004 at 03:01:31PM -0400, Geoff Thorpe wrote:
> On June 19, 2004 01:37 pm, Alexandre Julliard wrote:
> > > way towards cutting the number of non-developers building from source
> > > down to zero.
> >
> > I don't see why that should be a goal at all. You guys need to get rid
> > of
You mean link it with winelib when compiling, or build
a .so library you link in at runtime?
I mean creating what wine calls a winelib app: it uses wine magic for
startup (it ends up being a .so file run by the wine loader, and not a
full native ELF application).
By the way, how essential is STI
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
On Sun, Jun 20, 2004 at 06:21:58PM +0400, Vitaly Lipatov wrote:
> Please do not do it by default. Noone can parse my fstab
> correctly :)
Maybe it needs fixin' :)
--
Dimi.
On Sunday 20 June 2004 15:45, Mike Hearn wrote:
> On Sat, 19 Jun 2004 17:42:36 -0700, Alexandre Julliard wrote:
> > An initial set of symlinks will be created by
> > wineprefixcreate; they can then be modified with winecfg (or
> > by changing the symlinks by hand of course). The plan is
> > also to
On Sun, Jun 20, 2004 at 01:36:15PM +0300, Shachar Shemesh wrote:
> Shachar Shemesh wrote:
>
> I managed to solve the above problem by adding a "-shared name.spec" to
> the Makefile line that invokes the last winegcc. However, I think
> winemaker should have added that line itself. Is this a bug?
On Sat, 19 Jun 2004 16:22:01 -0700, Dan Kegel wrote:
> was practical to run. Here's part of its output. It looks as if
> the very first instruction accesses a null pointer in a strange
> way.
Actually scratch that, I don't know what I was thinking (not fully woken
up yet I suppose!). You're righ
On Sun, 20 Jun 2004 04:02:12 +0200, Ivan wrote:
> I have no idea, but X11drv doesn't initialize properly. This has been reported
> by users, I don't have x.org myself.
OK, that sounds like a bug in Wine rather than anything packaging related.
We should track it down and fix it.
More likely it's s
On Sat, 19 Jun 2004 16:22:01 -0700, Dan Kegel wrote:
>err:shell:SHGetFileInfoW pidl is null!
This is either a bug in the installer (in which case we should ignore it),
or some magic feature of SHGetFileInfo. From a quick read of MSDN and
Google I can't tell which, it looks like a bug but maybe
On Sat, 19 Jun 2004 17:42:36 -0700, Alexandre Julliard wrote:
> An initial set of symlinks will be created by wineprefixcreate; they
> can then be modified with winecfg (or by changing the symlinks by hand
> of course). The plan is also to have winecfg autodetect cdroms but
> that's not done yet.
Shachar Shemesh wrote:
Hi all,
I'm trying to create a winelib DLL project from scratch. You can
reproduce using the following steps:
create a file called "name.c", put the following content in it:
int func( int a )
{
return a+1;
}
Create a file called "name.spec". Put the following content in
Hi Christian - I tried to sent you an email but it bounced...
Are you sure that patch is correct (I've only glanced at it though!), as I
thought
the src1 was set from GetSrvcAndOpFromValue, and this should already handle
the
ONE_MINUS* type values?
Jason
emmanuel maillard a écrit :
Hi,
stack.c fail to build on ppc host due to CONTEXT_SEGMENTS flag, wich is
only define for i386 host.
ChangeLog:
Fix compilation error on non-i386 in stack_backtrace.
we shouldn't need the __i386__ tests in the winedbg code, except in the
CPU specific files (be_*.c).
19 matches
Mail list logo
