Re: Install i386 or amd64?

["Thomas Mueller" <mueller6724%bellsouth.net@localhost>]

> > > FYI no wine on latest FreeBSD 10.0-RELEASE amd64
> > > cd /usr/ports/emulators/wine ; make
> > >         ===>  wine-1.6.1,1 is only for i386, while you are running amd64.
> > > cd /usr/ports/emulators/wine-devel ; make
> > >         ===>  wine-devel-1.7.8,1 is only for i386, while you are running 
> > > amd64.
 
> > > Cheers,
> > > Julian
  
> > I believe there is early development for 64-bit wine, but that comes from 
> > winehq.org.

> > Early development is not good enough for productive use or for adding to 
> > FreeBSD ports.

> > But i386 wine can be run from amd64 and will run 32-bit but not 64-bit 
> > MS-Windows apps.

> > Or does this not work on FreeBSD 10.0-RELEASE amd64?

> See above for as I thought it was:
  {
>   I've always trusted that error message to be correct, so I've never
>   bothered to explicity ignore it & take time to manually hand force
>   an install to then test.

>   ( I don't want any MS programs except very occasionaly GPS, camera
>     & phone device loaders, & they'd most likely fail as an emulator
>     would also need to support USB ).
  }

> HOWEVER :-) I just found on FreeBSD current ports/
>         emulators/i386-wine-devel
> which means its available now !
  {
>   emulators/i386-wine-devel is not in FreeBSD-9.1 ports/ but is in
>   FreeBSD-9.2 & 10.0 ports/

>   i386-wine-devel on amd64 10.0-RELEASE, make install emits:
>         ===>  i386-wine-devel-1.7.8,1 binaries compiled for FreeBSD 8.3+ and 
> 9.1+ only.
>         *** Error code 1

>   amd64 FreeBSD-9.2-RELEASE emulators/i386-wine-devel compiles & installs !
>   wine gunzip.exe will run ! ...
>   ( well OK it brought up more screens & messages to think about,
>     which I wont pursue but you could. )

>   Confirmation here FreeBSD-9.2 ports/emulators/i386-wine-devel/Makefile.inc
>     COMMENT=32bit Microsoft Windows compatibility environment for 64bit 
> FreeBSD
 
>   Sources:
>     http://svnweb.freebsd.org/ports/head/emulators/i386-wine-devel/

>   I dont see a similarly named i386-wine-devel equivalent in NetBSD, just
>   
> http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/emulators/wine(|-(current|devel))/
  
>   So there'd be work to do, but it gives a start.

>   PS I'm not trying to tempt anyone from one BSD to another BSD,
>   but happy to see code sharing both ways, eg i386-wine Free > Net,
>   as& dev urtwn was Net to Free etc.
  }

> > Anyway, my wine installation is to be built on separate i386 installation 
> > which could be mounted on /compat/i386 when run from amd64.
>
> Tom
   
> Cheers,
> Julian
--
> Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com

I read the FreeBSD wiki page for i386-wine and saw that building under amd64 
required building an i386 installation to /compat/i386, so I figured it made 
more sense to install to a separate partition or removable disk such as USB, 
and the to use under amd64, mount on /compat/i386.

Julian, which BSDs do you work with?

I don't know if this would work for NetBSD, but I notice a bundle of COMPATs in 
GENERIC kernel config:

options         COMPAT_OSSAUDIO
options         COMPAT_NETBSD32
options         COMPAT_LINUX
options         COMPAT_LINUX32  # req. COMPAT_LINUX and COMPAT_NETBSD32
options         EXEC_ELF32
options         COMPAT_BSDPTY   # /dev/[pt]ty?? ptys.

But just because it's there doesn't mean it works, as I've found with NetBSD.

On building i386-wine, I am mainly interested in FreeBSD and Linux, since there 
are so many other things that can go wrong with NetBSD.

I've built modular (pkgsrc) xorg, and it either doesn't start at all, or mouse 
pointer moves horizontally but not up and down, meaning crippled.

X also fails to start in OpenBSD 5.4 live USB (liveusb-openbsd.sourceforge.net).

OpenBSD 5.3 live USB could startx, but mouse pointer was invisible but present, 
as I could see by which parts of the screen became active.

FreeBSD is much stabler than NetBSD on my hardware.

OpenBSD is crippled by lack of support for GPT and USB 3.0, meaning unable to 
read my hard drive.

DragonFlyBSD, in the latest release, dd'ed to USB stick, saw my hard-disk 
partitions but couldn't mount any, and I can't mount the DragonFly file system 
on the USB stick from FreeBSD or NetBSD.

But I am interested in the NetBSD code for devices re and athn.

Another instance of code porting, this time from OpenBSD to FreeBSD, was device 
rsu, which enables Internet access for my new computer with MSI Z77 MPOWER 
motherboard using Hiro H50191 USB-stick wireless adapter.

Tom