Date: Mon, 5 Aug 2013 02:31:54 -0400 From: "Sam Fourman Jr." <sfourman@gmail.com> To: Thomas Mueller <mueller6724@bellsouth.net> Cc: David Naylor <naylor.b.david@gmail.com>, freebsd-ports@freebsd.org Subject: Re: [REVIEW] Completing i386-wine Message-ID: <CAOFF%2BZ0Wrd825DtVj3CVnO=T6HWDR2xWabgpQVyUq38Nc_y1EA@mail.gmail.com> In-Reply-To: <638991.76970.bm@smtp107.sbc.mail.bf1.yahoo.com> References: <638991.76970.bm@smtp107.sbc.mail.bf1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Would there also be the possibility to have i386-wine as a source-code > port, and build from i386 installation? That avoids cross-compiling. > > One could build an i386 installation either from amd64 or previous i386 > installation, then build i386-wine and other desired ports when booted into > the i386 installation. > > This i386 installation would be on another partition or another disk (USB > 3.0 stick or USB 3.0 hard-drive partition?), and from the amd64 > installation, the i386 installation could be mounted on /compat/i386. > > With a USB hard drive, if not directly bootable, the loader and kernel > could be copied to another boot disk/partition, and root could be set for > the USB hard-drive partition. My USB 3.0 hard drive, Western Digital My > Book Essential, is not recognized by the BIOS/UEFI or GRUB2, but is > accessible from Linux or FreeBSD. > > Tom-- Can't we just have the port build wine in a i386 jail? eg it would require the FreeBSD sources, build the jail... etc.. it seems like a LOT, but honestly whats wrong with it... ill do the testing > Sam Fourman Jr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOFF%2BZ0Wrd825DtVj3CVnO=T6HWDR2xWabgpQVyUq38Nc_y1EA>