Windows programs no more running with the new wine-glibc
maxime.bellenge at laposte.net
Wed Nov 19 16:03:21 CST 2003
On Wed, 2003-11-19 at 21:29, Vincent Béron wrote:
> Le mer 19/11/2003 à 15:24, Sylvain Petreolle a écrit :
> > --- Vincent Béron <vberon at mecano.gme.usherb.ca> a écrit :
> > > What's the output of rpm -q prelink?
> > > What's the output of ldd /usr/bin/wine (or anything dynamically
> > > linked to libc)?
> > [syl at wine wine]$ rpm -q prelink
> > package prelink is not installed
> > [syl at wine wine]$ ldd /usr/local/bin/wine
> > libwine.so.1 => /usr/local/lib/libwine.so.1 (0x00111000)
> > libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00c45000)
> > libc.so.6 => /lib/tls/libc.so.6 (0x004e9000)
> > libdl.so.2 => /lib/libdl.so.2 (0x0090d000)
> > libm.so.6 => /lib/tls/libm.so.6 (0x00def000)
> > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00ef9000)
> If prelink is not installed, what you see here is very much probably the
> result of exec-shield.
> Does repeating ldd on the same file yields the same results, or do they
> differ each time?
I have the same configuration as Sylvain (RH9 -> Fedora Core 1)
and I have the same behavior. When I do a ldd wine I have always the
> > > Did you installed through an upgrade, or from scratch?
> > It was an upgrade from RH 9 Shrike (athlon) to Fedora beta3 and upgrade
> > via up2date.
I upgraded from RH9 to FC1 with the iso cds.
> So you somehow ended up without prelink (which I thought was part of the
> base install). Maybe that's a Fedora bug, but maybe not.
I do not have prelink installed too.
Maxime Bellengé <maxime.bellenge at laposte.net>
More information about the wine-devel