Please try these Wine build instructions?

kebabbert · 07-27-2007, 09:24 AM

I am trying to clean up several build instructions for Wine under Solaris x86. I have Solaris Express Community edition build 67. I want to write the wine instructions down, and put them somewhere on the web. To do that, I need some assistance. Could someone please try these build instructions to get Wine running? It seems to compile fine for me, but I want to see if these instructions work for several other machine setups.
Here is more info about Wine (which allows you to run Windows program on Solaris): www.winehq.org
Should I add these instructions to my Solaris noob guide, or do they work only for my machine?

1. Downloaded the latest wine (0.9.41) from
http://sourceforge.net/project/showf...ckage_id=77449

2. set up the environment (I use `tcsh`, so these will need to be adapted for Bourne shell family):
setenv PATH ${PATH}:/usr/ccs/bin:/usr/sfw/bin; rehash
(just make sure /usr/ccs/bin and /usr/sfw/bin is in your PATH).

3. ran:
./configure --prefix=/opt/abcd/ --sysconfdir=/etc/opt/abcd/ --mandir=/opt/abcd/share/man --datadir=/var/opt/abcd

4. ran `gmake`.

EDIT: Lot of people reports greatest success with Doug Scott's build instructions further down here. Use Doug Scott's Wine build instructions. It also seems as his instructions require OpenSolaris (Solaris Express), and are troublesome under plain Solaris 10.

kebabbert · 07-27-2007, 11:19 AM

Ok, it compiled fine for me with no errors. Are someone else getting errors?

jlliagre · 07-31-2007, 08:29 AM

I just tried with the 0.9.42 version.

I had that warning at the end of the configure command:

Code:

configure: WARNING: FontForge is missing.
Fonts will not be built. Dialog text may be invisible or unaligned.

Then the compilation failed at that stage:

Code:

gmake[2]: Entering directory `/tmp/wine-0.9.42/dlls/ntdll'
gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith  -g -O2  -o actctx.o actctx.c
actctx.c:76: error: `version' defined as wrong kind of tag
gmake[2]: *** [actctx.o] Error 1
gmake[2]: Leaving directory `/tmp/wine-0.9.42/dlls/ntdll'
gmake[1]: *** [ntdll] Error 2
gmake[1]: Leaving directory `/tmp/wine-0.9.42/dlls'
gmake: *** [dlls] Error 2

That was a name clash with an enum, I fixed it by replacing all "struct version" by "struct actctx_version" in the actctx.c file.

After that, everything compiles.

I installed the build but it appears to be unstable, perhaps because of a lack of configuration (I just created ~/.wine).

The notepad crashes after leaving any menu with:

Code:

/tmp/wine-0.9.42 $ /opt/wine/bin/notepad
Warning: the specified Windows directory L"c:\\windows" is not accessible.
Warning: the specified System directory L"c:\\windows\\system32" is not accessible.
Warning: could not find DOS drive for current working directory '/tmp/wine-0.9.42', starting in the Windows directory.
Warning: the specified Windows directory L"c:\\windows" is not accessible.
Warning: the specified System directory L"c:\\windows\\system32" is not accessible.
Warning: could not find DOS drive for current working directory '/', starting in the Windows directory.
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Resource id in failed request:  0x440000f
  Serial number of failed request:  182
  Current serial number in output stream:  182

kebabbert · 07-31-2007, 08:57 AM

Ok, just what I suspected. The fontforge package is used to generate fonts that wine uses, I believe. So it should be installed first maybe?

When running wine for the first time, there are programs in /wine/bin
that is called winecfg etc. One of them sets up your config files automaticallye for you, and then your last error msgs disappears. You should delete .wine and let it automatically get created.

I have other build instructions for wine too, somewhere. That works.

jlliagre · 07-31-2007, 09:05 AM

winecfg crashes:

Code:

$ rm -rf ~/.wine
$ /opt/wine/bin/winecfg
wine: creating configuration directory '/home/jlliagre/.wine'...
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Resource id in failed request:  0x4400003
  Serial number of failed request:  59
  Current serial number in output stream:  59
wine: wineprefixcreate failed while creating '/home/jlliagre/.wine'.
$  : No such file or directory
 : No such file or directory
wineserver: could not save registry branch to /home/jlliagre/.wine-FEVWLx/system.regwineserver: could not save registry branch to /home/jlliagre/.wine-FEVWLx/user.reg

kebabbert · 08-01-2007, 01:42 PM

Doug Scott writes:

CBE WINE BUILD INSTRUCTIONS - V1.0
----------------------------------

Step 1: [OPTIONAL] Add new user to do builds
- User requires "Software Installation" profile for CBE

root@db1> useradd -g sysadmin -d /export/home/cbe -m -s /usr/bin/bash -c "CBE build user" -P "Software Installation" cbe

Create a suitable /export/home/cbe/.bash_profile

root@db1> su - cbe

Step 2: Download and extract CBE

cbe@db1> wget -O - http://dlc.sun.com/osol/jds/download...-1.6.0-src.tar | tar fx -

Step 3: Remove SUNWsmbaS from JDS_DEPENDENCIES in jds-cbe-1.6.0/cbe-install
- Required for later SXCE builds as SUNWsmbaS is not installed

cbe@db1> chmod u+w jds-cbe-1.6.0/cbe-install
cbe@db1> printf "%%s/SUNWsmbaS//\nwq\n" | ex - jds-cbe-1.6.0/cbe-install

Step 4: Build and install CBE
- If you are not building JDS you can say no to installing dependencies
- This may take some time
cbe@db1> cd jds-cbe-1.6.0
cbe@db1> ./cbe-install

Step 5: Add env.sh to your .bash_profile
cbe@db1> cd ..
cbe@db1> printf ". /opt/jdsbld/bin/env.sh\n" >> .bash_profile
cbe@db1> . /opt/jdsbld/bin/env.sh

Step 6: Check out spec-files-extra
cbe@db1> svn co https://pkgbuild.svn.sourceforge.net...es-extra/trunk spec-files-extra

Step 7: Build
cbe@db1> cd spec-files-extra
cbe@db1> pkgtool build --download SFEfontforge.spec SFEfreetype.spec SFEwine.spec

This is using the CBE package system for Solaris. Just like blastwave, but it downloads the source automatically and compiles automatically for you. However, first the were was an compilation error, I first had to copy libgunicode.so.3 to /usr/lib and then compiling continued. But it would be better to a symlink i believe. This package also installs fontforge for you automatically.

The CBE package has also the latest vlc-player to download for Solaris (and lots of other stuff, like "GKrellm" which is a must - it displays info about your computer; memory, swap, etc. Go to it's web site). However, I couldnt get vlc to work. So if you succeed with vlc player I would be happy to know. The only issue is that it crashes when playing mpeg4, otherwise it works perfectly.

jlliagre · 08-01-2007, 03:53 PM

Why are you imposing bash ?

Both links are broken in your posting.

First one should probably be:
http://dlc.sun.com/osol/jds/download...-1.6.0-src.tar

Can you fix the second link ?

kebabbert · 08-02-2007, 03:31 AM

Both links are broken? Hmmm... weird. What happens if you just cut & copy the text into shell?

The reason it is bash, is because Doug Scott wrote his instructions that way. Im a real noob, and couldnt have come up with those, neither could I modify the instructions.

kebabbert · 08-02-2007, 03:32 AM

Here are the two broken links

Code:

http//dlc.sun.com/osol/jds/downloads/cbe/jds-cbe-1.6.0-src.tar  | tar fx -



https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk spec-files-extra

I dont get it, why are the broken links shown with "..." in the middle of the string? I had to put code-tags around to fix it.

LAN-Dominator.nl · 08-24-2007, 03:53 PM

What th ........

Look:

Code:

$ bunzip2 wine-0.9.44.tar.bz2
$ tar -xf wine-0.9.44.tar
tar: pax_global_header: typeflag 'g' not recognized, converting to regular file
$ setenv PATH ${PATH}:/usr/ccs/bin:/usr/sfw/bin; rehash
/bin/ksh: setenv:  not found
/bin/ksh: rehash:  not found
$

ps. i work under the KDE (OpenWindow Envoriment) version of Solaris

jlliagre · 08-24-2007, 04:32 PM

Try gtar (Gnu tar) and use your shell's syntax for setting the PATH.

LAN-Dominator.nl · 08-26-2007, 05:08 AM

how do i put the path under the shell's syntax?

LAN-Dominator.nl · 08-26-2007, 05:11 AM

i download a MAKE-program, but got this error:

Code:

$ su
Password:
# cd make-3.81
# sh configure
checking for a BSD-compatible install... config/install-sh -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... no
checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
#

LAN-Dominator.nl · 08-26-2007, 05:17 AM

download GNU-TAR, but when trying to install:

Code:

# cd ../
# gunzip tar-1.18.tar.gz
# tar -xf tar-1.18
tar: tar-1.18: No such file or directory
# ^C
# tar -xf tar-1.18.tar
# cd tar-1.18
# ./configure
checking for a BSD-compatible install... build-aux/install-sh -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... no
checking how to create a ustar tar archive... plaintar
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
#

jlliagre · 08-26-2007, 05:47 AM

Why are you downloading and trying to install make and gnu tar while their binaries are already bundled with Solaris ?

Just add their location to your PATH.

PATH=$PATH:/usr/sfw/bin:/usr/ccs/bin

cc is possibly also there in /opt/SUNWspro/bin.