Mike Hearn wrote:
Hi,
The downloads page advertises support for 10.1, 10.0 and 9.2 Mandrake
packages but it seems only 10.1 RPMs are provided. Should the download
page be updated to say only 10.1 is available?
I'd rather actually it was built on an older Mandrake and then fixed to
work on
Hi,
The downloads page advertises support for 10.1, 10.0 and 9.2 Mandrake
packages but it seems only 10.1 RPMs are provided. Should the download
page be updated to say only 10.1 is available?
I'd rather actually it was built on an older Mandrake and then fixed to
work on later versions t
On Thu, 2004-01-08 at 22:44, Alexandre Julliard wrote:
> Well, it could maybe be added as an option, but I don't think it would
> work in all cases, since it will necessarily add different constraints
> on the layout (for instance you need to hardcode that the dlls are in
> ../lib/wine relative to
Mike Hearn <[EMAIL PROTECTED]> writes:
> Would you accept a patch to use this code on Linux systems to figure out
> where to load the DLLs from? That way Wine can be installed to any
> prefix and it works automatically, no need for wrapper scripts or
> anything like that.
Well, it could maybe be
On Thu, 2004-01-08 at 22:06, Alexandre Julliard wrote:
> Actually there used to be a reason to do that, when dlls needed to be
> in the Unix library path to get loaded properly. The default was to
> add symlinks in /usr/lib, but it wasn't very clean to have a bunch of
> dlls in there so it made sen
Mike Hearn <[EMAIL PROTECTED]> writes:
> The problem with this is that it's different to the layout used by the
> source installs, so giving tech support on #winehq etc becomes that much
> harder. It seems to be different simply for the sake of being different.
Actually there used to be a reason
> These are all libraries that belong to /usr/lib.
> All others (.dll.so dlls must go to /usr/lib/wine/).
>
> libwine.so will look and find them in /usr/lib/wine/ by default when trying to
load them.
>
> There is NO need to add /usr/lib/wine to ld.so.conf!
OK, I'll change this in this months buil
On Thu, 2004-01-08 at 21:10, Ivan Leo Murray-Smith wrote:
> libs are in /usr/lib/wine and dlls are in /usr/lib/wine/dlls, not adding
> /usr/lib/wine to ld.so.conf causes wine to fail, as it doesn't find
> ntdll.dll.so.
Works here. I only have /opt/wine/lib in my ld.so.conf, which doesn't
contain a
On Thu, Jan 08, 2004 at 10:10:59PM +0100, Ivan Leo Murray-Smith wrote:
> > Hmm, OK. I don't know which this person was using. Why is /usr/lib/wine
> > even added to ld.so.conf though, surely that isn't necessary? Only
> > libwine needs to be in the linker path.
> libs are in /usr/lib/wine and dlls
> Hmm, OK. I don't know which this person was using. Why is /usr/lib/wine
> even added to ld.so.conf though, surely that isn't necessary? Only
> libwine needs to be in the linker path.
libs are in /usr/lib/wine and dlls are in /usr/lib/wine/dlls, not adding
/usr/lib/wine to ld.so.conf causes wine t
On Thu, 2004-01-08 at 20:59, Ivan Leo Murray-Smith wrote:
> > Could whoever is responsible for these packages please double check the
> > specfiles?
> Never heard of such a problem, all RPMs are tested on both mdk 9.2 and 9.1, on 2
> different computers, and I've never noticed any lib problem. /usr
> Could whoever is responsible for these packages please double check the
> specfiles?
Never heard of such a problem, all RPMs are tested on both mdk 9.2 and 9.1, on 2
different computers, and I've never noticed any lib problem. /usr/lib/wine is
added to ld.so.conf during post, and after that ldcon
Hi,
I don't know who maintains the mandrake packages, but it appears that they
incorrectly install libwine.so.1 into /usr/lib/wine instead of /usr/lib,
and therefore all Wine apps fail to start with an unresolved import
failure.
Could whoever is responsible for these packages please double
13 matches
Mail list logo
