Re: wine (-devel) and i386-wine
from David Naylor (excerpt): If you are going to have a /compat/i386 chroot then you could install (normal 32bit) wine there and with the correct scripts run wine from that chroot without needing i386-wine at all (you will need to set up the correct PATH, LD_32_LIBRARY_PATH and LD_32_LIBRARY_PATH_RPATH variables). Alternatively, you could install wine on 32-bit and i386-wine on 64-bit and use those respectively. I hope this clarifies. That helps! I think I tried to install i386-wine, but now I will try with plain wine, or wine-devel. This would be on a separate partition so as to be able to run independently of amd64 installation. Then for amd64, I could mount this partition on /compat/i386 and would have to set up the scripts to run wine from that chroot. I had this problem on a previous installation, remember asking questions. That was on a hard drive that went bad (amd64 installation part), and while I recovered most user data, wine configuration and also i3 window manager configuration were lost. I believe if you build i386-wine only to run on amd64, you don't need Xorg for i386, but in my situation, I will need Xorg for both amd64 and i386. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: wine (-devel) and i386-wine
Hi Tom, On Monday, 1 September 2014 22:24:57 Thomas Mueller wrote: I read something about two days on www.freshports.org about wine and i386-wine that alters my plans. I tried to build i386-wine from i386 with the idea of using it both from i386 and amd64, in the latter case mounting the i386 partition on /compat/i386. But what I see makes that look not feasible. It is feasible to run the i386-wine ports from a 32bt environment - however it is not ideal. The port implements various hacks to get the package to work properly on an amd64 system that is simply not needed when running natively. If I want to run wine from both i386 and amd64 (not at the same time), do I need to make separate installations on separate partitions? In that case, how do I avoid wasteful duplication in compiling? I am getting ready to rebuild/update FreeBSD-current and possibly 10.0-STABLE from source, am planning to also make a new i386 installation on a hard drive in a USB 2.0 and eSATA enclosure, using eSATA. I want to do this soon, at least for FreeBSD-current because, after running svn up on FreeBSD src tree from NetBSD, I saw an update in $SRCDIR/sys/dev/re/if_re.c and want to see if that works on my Ethernet. I also want the new NFS improvements. If you are going to have a /compat/i386 chroot then you could install (normal 32bit) wine there and with the correct scripts run wine from that chroot without needing i386-wine at all (you will need to set up the correct PATH, LD_32_LIBRARY_PATH and LD_32_LIBRARY_PATH_RPATH variables). Alternatively, you could install wine on 32-bit and i386-wine on 64-bit and use those respectively. I hope this clarifies. Regards signature.asc Description: This is a digitally signed message part.
wine (-devel) and i386-wine
I read something about two days on www.freshports.org about wine and i386-wine that alters my plans. I tried to build i386-wine from i386 with the idea of using it both from i386 and amd64, in the latter case mounting the i386 partition on /compat/i386. But what I see makes that look not feasible. If I want to run wine from both i386 and amd64 (not at the same time), do I need to make separate installations on separate partitions? In that case, how do I avoid wasteful duplication in compiling? I am getting ready to rebuild/update FreeBSD-current and possibly 10.0-STABLE from source, am planning to also make a new i386 installation on a hard drive in a USB 2.0 and eSATA enclosure, using eSATA. I want to do this soon, at least for FreeBSD-current because, after running svn up on FreeBSD src tree from NetBSD, I saw an update in $SRCDIR/sys/dev/re/if_re.c and want to see if that works on my Ethernet. I also want the new NFS improvements. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
