marko10_000
/
wine-wine
forked from Mirrors/wine-wine
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update information concerning FreeBSD. 

Refer to Wine instead of wine as the package name.
oldstable
Gerald Pfeifer 2001-07-20 17:56:59 +00:00 committed by Alexandre Julliard
parent e12d8ae06e
commit d2b22894a0
1 changed files with 7 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README
View File

@ -14,7 +14,7 @@ that you wrote it.
2. QUICK START
Whenever you compile from source, it is recommended to use the Wine
Installer to build and install wine. From the top-level Wine
Installer to build and install Wine. From the top-level Wine
directory (which contains this file), run:
./tools/wineinstall
@ -29,7 +29,7 @@ especially the wealth of information found at http://www.winehq.com.
To compile and run Wine, you must have one of the following:
Linux version 2.0.36 or above
FreeBSD-current or FreeBSD 3.0 or later
FreeBSD 4.x or FreeBSD 5-CURRENT
Solaris x86 2.5 or later
Linux info:
@ -42,22 +42,14 @@ Linux info:
you may want to upgrade to at least the latest 2.0.x release.
FreeBSD info:
On FreeBSD, you may want to apply an LDT sharing patch too
(unless you are tracking -current where it finally has
been committed just recently), and there also is a small sigtrap
fix that's needed for wine's debugger. (Actually now that it's using
ptrace() by default it may no longer make a difference but it still
doesn't hurt...) And if you're running a system from the -stable
branch older than Nov 15 1999, like a 3.3-RELEASE, then you also
need to apply a signal handling change that was MFC'd at that date.
Make sure you have the USER_LDT, SYSVSHM, SYSVSEM, and SYSVMSG options
turned on in your kernel.
More information including patches for the -stable branch is in
the ports tree:
More information including patches for the 4-STABLE branch is in the
ports tree:
ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports/emulators/wine/files/
Solaris info:
You will most likely need to build wine with the GNU toolchain
You will most likely need to build Wine with the GNU toolchain
(gcc, gas, etc.)
Wine requires kernel-level threads to run. Currently, only Linux
@ -68,7 +60,7 @@ in the future.
You need to have the X11 development include files installed
(called xlib6g-dev in Debian and XFree86-devel in RedHat).
To use wine's support for multi-threaded applications, your X libraries
To use Wine's support for multi-threaded applications, your X libraries
must be reentrant, which is probably the default by now.
If you have libc6 (glibc2), or you compiled the X libraries yourself,
they were probably compiled with the reentrant option enabled.
@ -82,7 +74,7 @@ and xpm4g-dev. SuSE calls these packages xpm and xpm-devel.
On x86 Systems gcc >= 2.7.2 is required.
Versions earlier than 2.7.2.3 may have problems when certain files
are compiled with optimization, often due to problems with header file
management. pgcc currently doesn't work with wine. The cause of this problem
management. pgcc currently doesn't work with Wine. The cause of this problem
is unknown.
You also need flex version 2.5 or later and yacc.