Windows programs no more running with the new wine-glibc
Kevin DeKorte
kdekorte at yahoo.com
Wed Nov 19 09:48:10 CST 2003
All,
I am able to use prelinking and wine on my fedora system. Here is how I did it
first I undid all the prelinking with
prelink -a -u
Then I editted /etc/sysconfig/prelink to have these options
PRELINK_OPTS="-m --no-exec-shield"
then I ran prelink with the following options
prelink -a -m --no-exec-shield
And wine has ran fine for me ever since.
kdekorte at localhost bin]$ ldd wine
libwine.so.1 => /usr/local/lib/libwine.so.1 (0x40017000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x412a2000)
libc.so.6 => /lib/tls/libc.so.6 (0x41018000)
libdl.so.2 => /lib/libdl.so.2 (0x41177000)
libm.so.6 => /lib/tls/libm.so.6 (0x41153000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x41000000)
[kdekorte at localhost bin]$
Kevin
On Wednesday 19 November 2003 8:04 am, Vincent Béron wrote:
> Le mer 19/11/2003 à 02:39, Sylvain Petreolle a écrit :
> > Can this be applied to all Linux systems ? A Google search on
> > PRELINK_OPTS gives only 4 results and a locate on my Yarrow system
> > doesnt find any 'prelink' file.
>
> What's the output of rpm -q prelink?
> Did you installed through an upgrade, or from scratch?
> What's the output of ldd /usr/bin/wine (or anything dynamically linked
> to libc)?
>
> Vincent
More information about the wine-devel
mailing list