How to start wine?
Thomas Mueller
mueller6724 at bellsouth.net
Mon Aug 26 18:58:19 UTC 2013
What are LD_LIBRARY_PATH and LD_32_LIBRARY_PATH supposed to be? I see neither of these environment variables defined.
And what about PATH?
I am trying
#!/bin/sh
set PATH=/compat/i386/usr/local/bin:/compat/i386/usr/local/sbin:/compat/i386/usr/bin:/compat/i386/usr/sbin:/compat/i386/bin:/compat/i386/sbin:$PATH
export LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_32_LIBRARY_PATH
export LD_LIBRARY_PATH=/compat/i386/usr/local/lib:/compat/i386/usr/lib:/compat/i386/lib:$LD_LIBRARY_PATH
but I feel like I'm just thrashing here, will run into trouble trying to execute 32-bit binaries when not appropriate.
I see
/lib
/libexec
/usr/lib
/usr/lib32
/usr/libdata
/usr/libexec
/usr/local/lib
/usr/local/libdata
/usr/local/libexec
and then there are some subdirectories of these directories
with the FreeBSD i386 installation not mounted.
I have seen LD_LIBRARY_PATH before from building packages from source.
I thought maybe wineboot would set up the environment, but it looks like I have to set up the environment beforehand.
What is the difference between the various wine ports in $PORTSDIR/emulators? I used wine-devel, newer but less tested than wine.
Upstream latest release is 1.6 as far as I can see.
Building X for FreeBSD i386 before wine would be necessary for running from i386 boot even if not runnable from amd64.
My i386 version was/is somewhat behind amd64 version.
Tom
More information about the freebsd-ports
mailing list