Re: [Request for feedback] Improved DirectX in Wine ports (packages available)
On Friday, 6 June 2014 16:43:19 Alexandr Krivulya wrote:
> Hi!
> Can anyone tell me - this repo is still available? I can't install:
>
> pkg:
> http://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/dbn/repos/wine-cs/f
> reebsd:11:x86:64/digests.txz: Not Found
> pkg: Unable to find catalogs
>
> Or I do something wrong? Link from wiki i386-Wine page gives 404 error
> http://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/dbn/repos/wine/
Hi Alexandr,
You didn't do anything wrong. There is some kind of change happening with the
content delivery network. Please update the URL in wine-cs.conf to:
http://distcache.FreeBSD.org/local-distfiles/dbn/repos/wine-cs/${ABI}
I will update the wiki and the files shortly.
Regards
signature.asc
Description: This is a digitally signed message part.
Re: [Request for feedback] Improved DirectX in Wine ports (packages available)
Hi, I made an error in the wine-cs.conf file below. Instead of installing i386- wine-cs it was directed to the normal wine repository. If you used the repo approach to install wine-cs please try again (I have fied the wine-cs.conf file). Regards On Monday, 31 March 2014 20:58:50 David Naylor wrote: > Hi, > > It has been requested by some community members that the custom DirectX > patches by stefand [1] be integrated into the Wine port. As this requires > a non-trivial amount of work I would like to assess the community's > interest in these patches. > > For those who do not know what these patches do: it is reported that they > improve the performance of DirectX games and could possibly fix regressions > on FreeBSD. > > To try out the packages please either install the packages directly from the > mirrors [2] or issue the following commands: # mkdir -p > /usr/local/etc/pkg/repos > # fetch -o /usr/local/etc/pkg/repos \ > http://people.freebsd.org/~dbn/repos/wine-cs.conf > # fetch -o \ > /usr/local/etc/pkg/repos http://people.freebsd.org/~dbn/repos/wine-cs.cert > # pkg update > # pkg install -r wine i386-wine-cs > > The packages, although labelled 1.7.15 (for the Wine version they are based > on) are based on cs-0.6. > > If you find the packages useful, please report back to me. If there is > sufficient support (i.e. enough people reply in the positive) then I'll > publish the packages on a regular basis and maintain the appropriate ports. > > Regards > > [1] https://github.com/stefand/wine/releases > [2] > http://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/dbn/repos/wine-cs/ signature.asc Description: This is a digitally signed message part.
Re: [Request for feedback] Improved DirectX in Wine ports (packages available)
Hi Johannes On Wednesday, 2 April 2014 13:00:04 Johannes Meixner wrote: > Hi, > > Ricing wine sounds like a great idea. > > Could you please publish the WIP of the port you've generated the packages > from? All I did was create a patch between Wine-1.7.15 and cs-0.6, and put that patch in the port's files/. Although not strictly correct it is enough for testing purposes. Regards signature.asc Description: This is a digitally signed message part.
Re: [Request for feedback] Improved DirectX in Wine ports (packages available)
On Monday, 31 March 2014 22:36:09 ill...@gmail.com wrote: > On 31 March 2014 13:58, David Naylor wrote: > > Hi, > > > > It has been requested by some community members that the custom DirectX > > patches by stefand [1] be integrated into the Wine port. As this > > requires a non-trivial amount of work I would like to assess the > > community's interest in these patches. > > > > For those who do not know what these patches do: it is reported that they > > improve the performance of DirectX games and could possibly fix > > regressions on FreeBSD. > > > > To try out the packages please either install the packages directly from > > the mirrors [2] or issue the following commands: # mkdir -p > > /usr/local/etc/pkg/repos > > # fetch -o /usr/local/etc/pkg/repos > > http://people.freebsd.org/~dbn/repos/wine-cs.conf # fetch -o > > /usr/local/etc/pkg/repos > > http://people.freebsd.org/~dbn/repos/wine-cs.cert # pkg update > > # pkg install -r wine i386-wine-cs > > > > The packages, although labelled 1.7.15 (for the Wine version they are > > based on) are based on cs-0.6. > > > > If you find the packages useful, please report back to me. If there is > > sufficient support (i.e. enough people reply in the positive) then I'll > > publish the packages on a regular basis and maintain the appropriate > > ports. > > > > Regards > > > > [1] https://github.com/stefand/wine/releases > > [2] > > http://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/dbn/repos/wine-c > > s/ > It would be a pleasant change, assuming it doesn't cause occasional > lockups. Are there any particular applications that would be worth > testing (I doubt the ancient stuff I occasionally run under wine will > be heavily influenced by these improvements)? Any 3D, or DirectX, program that does not run with sufficient performance or reliability could benefit from this. If your "ancient stuff" runs well enough for you then alas no improvement possible. signature.asc Description: This is a digitally signed message part.
[Request for feedback] Improved DirectX in Wine ports (packages available)
Hi, It has been requested by some community members that the custom DirectX patches by stefand [1] be integrated into the Wine port. As this requires a non-trivial amount of work I would like to assess the community's interest in these patches. For those who do not know what these patches do: it is reported that they improve the performance of DirectX games and could possibly fix regressions on FreeBSD. To try out the packages please either install the packages directly from the mirrors [2] or issue the following commands: # mkdir -p /usr/local/etc/pkg/repos # fetch -o /usr/local/etc/pkg/repos http://people.freebsd.org/~dbn/repos/wine-cs.conf # fetch -o /usr/local/etc/pkg/repos http://people.freebsd.org/~dbn/repos/wine-cs.cert # pkg update # pkg install -r wine i386-wine-cs The packages, although labelled 1.7.15 (for the Wine version they are based on) are based on cs-0.6. If you find the packages useful, please report back to me. If there is sufficient support (i.e. enough people reply in the positive) then I'll publish the packages on a regular basis and maintain the appropriate ports. Regards [1] https://github.com/stefand/wine/releases [2] http://ftp.freebsd.org/pub/FreeBSD/ports/local-distfiles/dbn/repos/wine-cs/ signature.asc Description: This is a digitally signed message part.
i386-wine(-devel) packages available for FreeBSD 10.0 and current
Hi All, Please be advised that packages for i386-wine(-devel) are now available for FreeBSD/amd64 10.0 and current. The packages can be obtained from the wiki [1], via ports [2] or the official FreeBSD package repository. Enjoy, [1] https://wiki.freebsd.org/i386-Wine [2] See emulators/i386-wine and emulators/i386-wine-devel from the Ports Collection signature.asc Description: This is a digitally signed message part.
Re: wine-fbsd64-1.5.24 on amd64 complains that OpenGL rendering is disabled
On Thursday, 7 November 2013 11:46:46 Yuri wrote: > On 11/07/2013 06:12, David Naylor wrote: > > The wine-fbsd64 line of packages were discontinued in favour of the > > i386-wine port. The i386-wine is the same as the wine-fbsd64 except it > > is officially part of the Port's Collection. > > > > Please seehttps://wiki.freebsd.org/i386-Wine for details and update to > > the > > latest version of wine (1.7.5), and please let me know if this fixes the > > problem. > > I see, I had the wrong version installed. But now, with > i386-wine-devel-1.7.5,1, it also prints the error message: > err:wgl:X11DRV_WineGL_InitOpenglInfo couldn't initialize OpenGL, expect > problems Could you please send me the output from running: sh -x /usr/local/share/wine/patch-nvidia.sh Also, could you please research WINEDEBUG, setting that environment variable to the correct values could result in the root cause of your troubles (sorry, I don't have time right now to give you the correct parameters, and my memory is not that good :-( ). > I also would like to suggest you change the message for emulators/wine. > Currently it says: > ===> wine-1.6,1 is only for i386, while you are running amd64. > It should say: "emulators/wine is discontinued on all platforms, please > use emulators/i386-wine or emulators/i386-wine-devel" > Because most people don't know such details about the current state of > wine port development. I've passed on your suggestion to the maintainer of emulators/wine. For the record, emulators/wine is not discontinued and is the prefered port for 32-bit systems but it does not work under amd64 (which is where i386-wine comes in). Regards signature.asc Description: This is a digitally signed message part.
Re: wine-fbsd64-1.5.24 on amd64 complains that OpenGL rendering is disabled
On Wednesday, 6 November 2013 17:22:03 Yuri wrote: > On 11/06/2013 10:50, David Naylor wrote: > > Have you installed the latest version of wine (available at > > emulators/i386- > > > > wine-devel) and have you run: > > /usr/local/share/wine/patch-nvidia.sh > > > > Otherwise I can help you with this problem (I am the maintainer of the > > port). > Hi David, > > I have wine-1.5.24,1 installed on 9.2 STABLE amd64. I think this is the > last version. > Running /usr/local/share/wine/patch-nvidia.sh doesn't help the problem. The wine-fbsd64 line of packages were discontinued in favour of the i386-wine port. The i386-wine is the same as the wine-fbsd64 except it is officially part of the Port's Collection. Please see https://wiki.freebsd.org/i386-Wine for details and update to the latest version of wine (1.7.5), and please let me know if this fixes the problem. Regards signature.asc Description: This is a digitally signed message part.
Re: wine-fbsd64-1.5.24 on amd64 complains that OpenGL rendering is disabled
Hi Yuri Have you installed the latest version of wine (available at emulators/i386- wine-devel) and have you run: /usr/local/share/wine/patch-nvidia.sh Otherwise I can help you with this problem (I am the maintainer of the port). Regards On Wednesday, 6 November 2013 01:08:36 Yuri wrote: > I am trying to run Half Life 2 (hl2.exe), and am getting this message: > err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, > most likely your OpenGL drivers haven't been installed correctly (using > GL renderer "GeForce GT 610/PCIe/SSE2", version "1.4 (2.1.2 NVIDIA > 319.32)"). > err:d3d:WineD3D_CreateFakeGLContext Failed to find a suitable pixel format. > err:d3d:wined3d_adapter_init Failed to get a GL context for adapter > 0x1319d8. > > glxinfo | grep -i render says that direct rendering is enabled, and it > indeed works. > nvidia-driver-319.32, FreeBSD 9.2 STABLE > > WineHQ lists Half Life 2 as working in wine. > > Anybody knows why does FreeBSD version of wine fails to run OpenGL? > > Yuri signature.asc Description: This is a digitally signed message part.
Re: Why linuxlator rejects libc.so.6 for sligtly newer GNU/Linux 2.6.24 ?
On Sunday, 21 July 2013 10:49:19 Yuri wrote: > I am trying to run one Linux program on 9.1 amd64. > I copied all relevant shared libraries from Ubuntu and set the directory > with LD_LIBRARY_PATH and libc.so.6 with LD_PRELOAD. > The newer version of libc.so.6 causes the problem: loader for some > reason doesn't accept it and complains: > > ERROR: ld.so: object 'my-libs/libc.so.6' from LD_PRELOAD cannot be > preloaded: ignored. > > This special libc.so.6 is from GNU/Linux 2.6.24 > google-talk-libs/libc.so.6: ELF 32-bit LSB shared object, Intel 80386, > version 1 (SYSV), dynamically linked (uses shared libs), > BuildID[sha1]=0x81a55e819c61f581e6a9179eaf59726dd80aea31, for GNU/Linux > 2.6.24, stripped > While supplied with linux_base-f10-10_7 libc.so.6 is from GNU/Linux 2.6.9: > /compat/linux/lib/libc.so.6: ELF 32-bit LSB shared object, Intel 80386, > version 1 (SYSV), dynamically linked (uses shared libs), > BuildID[sha1]=0x4f5aefe82ff9a8102064d90e7a03c283b6751c39, for GNU/Linux > 2.6.9, not stripped > > Difference is only in the minor version. Why this library gets rejected? The short answer is that Linux does not follow a version system that most people are familiar with. Since the 2.6.x (and now 3.x) days the value of "2.6." and "3." have had no meaning. To my understanding the version number "x" does not guarantee backward compatibility for the KI/ABI/API (although syscall I think is backward compatible). So, on FreeBSD 9 the Linuxulator supports version 2.6.16, which is not feature compatible with 2.6.24 as the ".24" does not denote a bug fix level as most would understand but an arbitrary increase the the number (my view is that the Linux kernel version has no value other than a monotonically increases series, except for if and when it has a forth denomination). Googling will indicate more about the exact meaning of the Linux kernel version. signature.asc Description: This is a digitally signed message part.
Re: wine on 64-bit freebsd
On Tuesday, 2 July 2013 18:42:52 Alexandr wrote: > Hello! Hi > Can anyone tell me - do I need full 32-bit environment to run windows > applications as it described at https://wiki.freebsd.org/Wine? Please have a look at https://wiki.freebsd.org/i386-Wine for details on running wine on amd64 systems. > Without 32-bit environment with wine-fbsd64-1.5.24,1 I can run a few > simple applications (that don't need DirectX), but the most - no, even > 15-years old games. The best way to run 3D games is to have a nVidia graphics card and to use the binary nVidia drivers. Using open source drivers (such as intel) is theoretically possible however I have not succeeded in this (I'm working on the problem, when I have time). If you have any further questions please ask. Regards signature.asc Description: This is a digitally signed message part.
[PKGNG] i386-wine-1.6.r4
Hi,
Pkgng packages are available for i386-wine-1.6.r4 [1] at local-distfiles [2].
Currently packages are available for FreeBSD 8 and 9 [3]. For previous
version of i386-wine replace 'latest' with the version number.
To install the port try one of the following options:
Method 1 (Quick and easy)
=
If wine already installed:
# pkg delete i386-wine
For FreeBSD 8 (as root):
# pkg add http://alturl.com/ih93t
For FreeBSD 9 (as root):
# pkg add http://alturl.com/opzyj
Method 2 (Multi-repo mode: secure, preferred)
=
To setup the repo and do initial port install (as root):
# mkdir -p /usr/local/etc/pkg/repos
# fetch -o /usr/local/etc/pkg/repos \
http://people.freebsd.org/~dbn/repos/wine.conf
# fetch -o /usr/local/etc/pkg/repos \
http://people.freebsd.org/~dbn/repos/wine.cert
# pkg update
# pkg install -r wine i386-wine
Please consider editing /usr/local/etc/pkg/repos/wine.conf to use one of the
many available mirrors[2]. To install an older version of wine change the
suffix "latest" to a version listed on the wiki[1].
To update already installed port (as root)
# pkg upgrade -r wine
Regards
David
[1] See the wiki for more details: http://wiki.FreeBSD.org/i386-Wine
[2] See your local FreeBSD mirror under ports/local-distfiles/dbn/i386-wine-
devel/${ABI}/latest where ABI=freebsd:X:x86:64 for X in {8, 9}. For a list of
mirrors please see
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html
[3] Packages are built from FreeBSD 8.3 and 9.1 respectively.
signature.asc
Description: This is a digitally signed message part.
Fwd: [PKGNG] i386-wine-1.6.r2
Hi,
Pkgng packages are available for i386-wine-1.6.r2 [1] at local-distfiles [2].
Currently packages are available for FreeBSD 8 and 9 [3][4]. For previous
version of i386-wine replace 'latest' with the version number.
To install the port try one of the following options:
- Method 1 (Quick and easy)
For FreeBSD 8 (as root)
# pkg add http://alturl.com/ih93t
For FreeBSD 9 (as root)
# pkg add http://alturl.com/opzyj
- Method 2 (Repo)
This method will only be fully supported with pkgng v1.1.
Regards
David
P.S. I'll be available on Saturday to address any issues / questions.
[1] See the wiki for more details: http://wiki.FreeBSD.org/i386-Wine (WIP)
[2] See your local FreeBSD mirror under ports/local-distfiles/dbn/i386-wine-
devel/${ABI}/latest where ABI=freebsd:X:x86:64 for X in {8, 9}.
[3] Packages are built from FreeBSD 8.3 and 9.1 respectively.
[4] Packaging for FreeBSD 10 will be resumed in due course.
signature.asc
Description: This is a digitally signed message part.
[PKGNG] i386-wine-1.5.30
Hi,
Pkgng packages are available for i386-wine-1.5.30 [1] at local-distfiles [2].
Currently packages are available for FreeBSD 8 and 9 [3][4]. For previous
version of i386-wine replace 'latest' with the version number.
To install the port try one of the following options:
- Method 1 (Quick and easy)
For FreeBSD 8 (as root)
# pkg add http://alturl.com/4smzi
For FreeBSD 9 (as root)
# pkg add http://alturl.com/tn8mv
- Method 2 (Repo)
This method will only be fully supported with pkgng v1.1.
1) Set `PKG_MULTIREPOS' to `YES' in ${LOCALBASE}/etc/pkg.conf
2) Add repo `wine-devel' with URL [2] to ${LOCALBASE}/etc/pkg.conf
3) Install (as root):
# pkg install -r wine-devel i386-wine
or upgrade (as root):
# pkg upgrade -r wine-devel
Regards
David
P.S. I'll be available on Saturday to address any issues / questions.
[1] See the wiki for more details: http://wiki.FreeBSD.org/i386-Wine (WIP)
[2] See your local FreeBSD mirror under ports/local-distfiles/dbn/i386-wine-
devel/${ABI}/latest where ABI=freebsd:X:x86:64 for X in {8, 9}.
[3] Packages are built from FreeBSD 8.3 and 9.1 respectively.
[4] Packaging for FreeBSD 10 will be resumed in due course.
signature.asc
Description: This is a digitally signed message part.
Re: emulators/wine64: Questions re self-maintained port
Hi, This should be fixed in r317544, if you are able to compile from ports otherwise please await the announcement of the availability of new packages. Regards On Sunday, 24 March 2013 05:20:04 Beeblebrox wrote: > output of "# sh -x /usr/local/share/wine/patch-nvidia.sh -n" ==> > > + set -e > + PORTSDIR=/asp/ports > + PREFIX=/usr/local > + DISTDIR=/asp/distfiles > + [ -d /asp/distfiles ] > + cd /asp/distfiles > + NO_REMOVE_NVIDIA=yes > + getopt -n -n > + args=' -n --' > + [ 0 -ne 0 ] > + set -- -n -- > + true > + NO_FETCH=yes > + shift > + true > + shift > + break > + whoami > + [ root = root ] > + echo '===> Patching wine-fbsd64 to work with x11/nvidia-driver:' > + [ -z '' ] > + version wine-fbsd64 > + local ret pkg=wine-fbsd64 > + [ -f /usr/local/sbin/pkg ] > + pkg query -g %v wine-fbsd64 > + ret=1.5.24,1 > + [ -z 1.5.24,1 ] > + [ -z 1.5.24,1 ] > + echo 1.5.24,1 > + WINE=1.5.24,1 > + [ -n 1.5.24,1 ] > + echo '=> Detected wine-fbsd64: 1.5.24,1' > + version nvidia-driver > + local ret pkg=nvidia-driver > + [ -f /usr/local/sbin/pkg ] > + pkg query -g %v nvidia-driver > + ret='' > + NV='' > > > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/emulators-wine64-Questions-re-self-mai > ntained-port-tp5797622p5798606.html Sent from the freebsd-emulation mailing > list archive at Nabble.com. signature.asc Description: This is a digitally signed message part.
Re: emulators/wine64: Questions re self-maintained port
On Saturday, 23 March 2013 12:19:55 Beeblebrox wrote: > >> If you have time, I would like to diagnose the incorrect detection. > > Sure, glad to help. > > >> Do you perhaps have nvidia-driver port installed > > No Nvidia port, not even nvidia-texture-tools > make.conf has WITHOUT_NOUVEAU=yes > > >> or a stale $PREFIX/share/doc/NVIDIA_GLX-1.0/README? > > /usr/local/share/doc/wine and /usr/local/share/wine are dated Feb-16-13 > > Present state of my video car and Xorg (using xorg-devel port overlay): > http://freebsd.1045724.n5.nabble.com/quot-Radeon-HD-4200-quot-e17-and-gdm3-n > ot-working-td5796823.html > > Host: 10-Current, amd64. Let me know if you need any other info. Could you please run this command (as root), and sent me the output: # sh -x /usr/local/share/wine/patch-nvidia.sh -n This will not alter your system. For reference, my system gives: # sudo sh -x /usr/local/share/wine/patch-nvidia.sh -n + set -e + PORTSDIR=/usr/ports + PREFIX=/usr/local + DISTDIR=/usr/ports/distfiles + [ -d /usr/ports/distfiles ] + cd /usr/ports/distfiles + NO_REMOVE_NVIDIA=yes + getopt -n -n + args=' -n --' + [ 0 -ne 0 ] + set -- -n -- + true + NO_FETCH=yes + shift + true + shift + break + whoami + [ root = root ] + echo '===> Patching wine-fbsd64 to work with x11/nvidia-driver:' ===> Patching wine-fbsd64 to work with x11/nvidia-driver: + [ -z '' ] + version wine-fbsd64 + local ret pkg=wine-fbsd64 + [ -f /usr/local/sbin/pkg ] + pkg query -g %v wine-fbsd64 + ret='' + [ -z '' ] + pkg_info -E 'wine-fbsd64*' + cut -f 3 -d - + ret=1.5.24,1 + [ -z 1.5.24,1 ] + echo 1.5.24,1 + WINE=1.5.24,1 + [ -n 1.5.24,1 ] + echo '=> Detected wine-fbsd64: 1.5.24,1' => Detected wine-fbsd64: 1.5.24,1 + version nvidia-driver + local ret pkg=nvidia-driver + [ -f /usr/local/sbin/pkg ] + pkg query -g %v nvidia-driver + ret=310.32 + [ -z 310.32 ] + [ -z 310.32 ] + echo 310.32 + NV=310.32 + [ -n 310.32 ] + echo '=> Detected nvidia-driver: 310.32' => Detected nvidia-driver: 310.32 + NVIDIA=310.32 + echo 310.32 + cut -f 1 -d _ + cut -f 1 -d , + NV=310.32 + [ ! -f NVIDIA-FreeBSD-x86-310.32.tar.gz ] + [ -n yes ] + terminate 8 'NVIDIA-FreeBSD-x86-310.32.tar.gz unavailable' + echo '!!! NVIDIA-FreeBSD-x86-310.32.tar.gz unavailable !!!' !!! NVIDIA-FreeBSD-x86-310.32.tar.gz unavailable !!! + echo Terminating... Terminating... + exit 8 Regards signature.asc Description: This is a digitally signed message part.
Re: emulators/wine64: Questions re self-maintained port
On Friday, 22 March 2013 16:20:07 Beeblebrox wrote: > Hi David, thanks for answering. Not a problem. > First-off, I seem to have mis-understood the available downloads. I thought > that wine-1.5.x-freebsd10 was a source file when it2s a pkgng-ready binary - > so I just did "pkg add" to the file, it installed and it is working. Thanks > for that. :-) > My questions in the first post (although they have become somewhat > irrelevant at this point) were about: > > * self-maintained port is; let's say you found some source code you want to > try but it's not in the ports tree - you can create your own port for it and > compile it as if it were in the ports tree. So it's actually a bit similar > to what your diff script does. Okay, I understand you now. > * By options I very simply meant things like MASTER_SITES, IGNORE_SHA_ERROR, > etc. I have absolutely no experience in writng a Makefile... > > One thing I did find strange when I installed the wine*tbz, was that the > install script detected the video card as Nvidia. In fact, the card is a > Radeon HD 4200 (r600 driver). I'm also using Xorg from trunk, not ports. > make.conf has "WITHOUT_NOUVEAU=yes". Will this error hamper 3D performance? > "Installing wine-fbsd64-1.5.24,1...A NVIDIA GRAPHICS DRIVER HAS BEEN > DETECTED ON THIS SYSTEM AND THE AUTOMATED > PATCHING HAS FAILED, execute (as root) > sh /usr/local/share/wine/patch-nvidia.sh > to get 2D/3D acceleration to work with the nvidia driver. Without this wine > will crash when a program requires 2D/3D graphics acceleration." Thanks is strange. The detection is done using `pkg query` or `pkg_info` as appropriate. Do you perhaps have nvidia-driver port installed or a stale $PREFIX/share/doc/NVIDIA_GLX-1.0/README? If not, and you have time, I would like to diagnose the incorrect detection. On the user side, since you do not use the nvidia-driver, and the patching failed. You are good to go. :-) Regards signature.asc Description: This is a digitally signed message part.
Re: emulators/wine64: Questions re self-maintained port
Hi On Thursday, 21 March 2013 07:26:13 Beeblebrox wrote: > Hi folks, > As advised on the the wiki.freebsd.org/Wine site, I plan to download the > wine source from http://www.mediafire.com/wine_fbsd64 the > wine-1.5.x-freebsd10 also the wine-fbds64.diff file. What do you plan to do? The wine-fbsd64 patch is to create a wine port that will run i386 (read 32bit) Windows programs on FreeBSD amd64 (read 64bit). It is *not* a patch to run 64bit Windows on FreeBSD amd64. > I would like to create a self-maintained port for this download set, and Can you please clarify what a "self-maintained" port is? > need to pass some options to the Makefile so as to make my life easier. What options to you need passed? Are these port options and configure options? The packages available at mediafire have many port options enabled (i.e. it is not a build with the default options). > I > have directly copied the original emulators/wine folder into my folder of > self-maintained ports and have modified the original Makefile. I am however > stuck regarding how to do these: The wine-fbsd64.diff patch is used to create a separate port (called wine- fbsd64). That port is a slave to emulators/wine(-devel). > 1. Do not check sha256 of the source .txz file (modify distinfo or > Makefile?) > 2. The wine-fbds64.diff should be placed under the "files" folder I assume? > Will the Makefile then automatically invoke that file or must I modify the > Makefile for it to be taken into account? That patch could be better thought as a shar archive. Apply it to $PORTSDIR/emulators, then compile under an i386 environment. I will be creating a wiki over the weekend that will explain in detail how to use that patch/port (which will be committed to ports relatively soon). If you need clarity on any issue please ask :-) Regards, P.S. I am the maintainer of that patch. signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.24 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.24 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able to isolate where the problem is occurring (wine, ports, world, kernel, i386, amd64). A possible solution in to try upgrading, or downgrading, software used however I have not been able to fix the problem with my attempts. If you find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.24,1.tbz) = 7a69ce1f152ef9e5e1ad35e022bb4683 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.24.1.txz) = 18bd09208f4e983e9495b33d9fdadaae MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.24,1.txz) = 86361cc8b023d762f5e42a8fb226f5fe [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.23 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.23 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able to isolate where the problem is occurring (wine, ports, world, kernel, i386, amd64). A possible solution in to try upgrading, or downgrading, software used however I have not been able to fix the problem with my attempts. If you find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.23,1.tbz) = f70260cc6f50184348321cc33451c6a0 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.23.1.txz) = c9a75ab1b26852d89acebfaf1945c93a MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.23,1.txz) = 2f91dc746978990bb2c2953300539b36 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.22 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.21 have been uploaded to mediafire [2]. The packages for FreeBSD 10 have been temporarily discontinued due to build errors [3]. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able to isolate where the problem is occurring (wine, ports, world, kernel, i386, amd64). A possible solution in to try upgrading, or downgrading, software used however I have not been able to fix the problem with my attempts. If you find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.22,1.tbz) = a4c0b8454cee0af89525764e522c3c5c MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.22.1.txz) = 963a74f63b2b979e5ad0b792c0bfa3af [2] http://www.mediafire.com/wine_fbsd64 [3] I'm building using FreeBSD 9.1 system and a FreeBSD 10-current chroot. The error is "tar: getvfsbyname failed: No such file or directory". Likely a compatibility issue... signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.21 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.21 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able to isolate where the problem is occurring (wine, ports, world, kernel, i386, amd64). A possible solution in to try upgrading, or downgrading, software used however I have not been able to fix the problem with my attempts. If you find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.21,1.tbz) = cfe91a668242a5f8fea5f395adda4e15 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.21.1.txz) = 43fbfd9e4882f4098f62c57f15474ed9 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.21,1.txz) = 63cca726e420be570485d173e8ce12f5 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)
On 26 Dec 2012 9:28 AM, "Jens Jahnke" wrote: > > Hi, Hi, > On Mon, 24 Dec 2012 12:27:11 +0200 > David Naylor wrote: > > DN> Since it is possible to install the existing pkg > DN> packages in a pkgng environment (which I do) this is not a high > DN> priority. > > is there a documentation for that? I searched the pkgng docs but found > nothing regarding installation of "old" packages or converting them to > a newer version. Use the old `pkg_ng` command to install the package. As long as the files installed with the old and the new package tools are mutually exclusive you shouldn't have a problem. If you patch your ports tree with the wine-fbsd64 diff then it is possible to use `pkg2ng` to convert to the pkgng format. (Although I have never tested that, see documentation for pkg2ng and `pkg create`). Regards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine: Sony Reader for PC software in wine
Hi, On Tuesday, 25 December 2012 11:22:17 Matthias Apitz wrote: > Hello FreeBSD wine guru's, > > The software installs fine with wine 1.5.4 and it starts fine with: Could you try with a newer version of wine, wine up to 1.5.20 has been released. > $ wine Reader.exe > > One can connect fine to the Adobe ID server, import and read DRM'ed > epubs. What does not work is that the T1 on the USB devices is not seen. > > I have mounted the two USB devices as: > > /dev/da2 on /settings (msdosfs, local, read-only) > /dev/da0 on /reader (msdosfs, local) > > and configured wine (with winecfg) to see the devices as K: and F: which > works fine, for example, with the Explorer.exe; but the software > Reader.exe does not "see" the T1; it says on start: > > fixme:win:FlashWindowEx 0x33f228 > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections > will fail fixme:iphlpapi:NotifyAddrChange (Handle 0x79f6e0, overlapped > 0x100cf2a0): stub fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: > heap list snapshot fixme:toolhelp:Heap32ListFirst : stub > fixme:win:RegisterDeviceNotificationA (hwnd=0x700f8, > filter=0xb6ed48,flags=0x) returns a fake device notification > handle! fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! > fixme:win:FlashWindowEx 0x33d450 The line fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 suggests to me that wine does not implement some functionality that Reader.exe requires... > and in the GUI it says that the reader T1 is not connected. Perhaps > the software is reading somehow the USB bus directly and looking for the > vendorID and productID... > > How I could nail down, what it is missing? Thanks You could try appdb.winehq.org and see if the software is supported. The website may also suggest fixes for various issues. If there is no page for the software try filing a bug report, if there is a page then look through the bug reports to see if focus is given to fix it. It is possible that this is a FreeBSD specific problem, in which case submitting a bug report may be required. Lastly, look at documentation for the WINEDEBUG environment variable as that could provide more information as to the source of the error. Good luck. Regards, signature.asc Description: This is a digitally signed message part.
Re: Sound lag in Wine
Hi On Thursday, 20 December 2012 15:08:31 Ross wrote: > Hello. > > I installed David Naylor's wine-fbsd64-1.5.18. > Installed Steam, bought Counter-Strike 1.6 and CS: CZ. > > However, when I run these games I experience a sound lag (maybe a > half-second — second). I remember having a similar problem, although my issue was an echo. After a few updates the issue disappeared. > I googled the topic, the soultion is to switch to Alsa, which is not > supported in wine-fbsd64-1.5.18… > > Is there anything I can do to get rid of the lag? I can suggest three things to try: 1) Update software 1.1) Upgrade (or downgrade) wine (I've release version 1.5.20) 1.2) Upgrade ports (some sound related components may cause issues, although *very* unlikely) 1.3) Upgrade kernel and world (sound fixes may be available to fix your issue) 2) Try building your own wine package with ALSA support (requires a i386 jail/chroot, editing the emulators/wine-devel/Makefile and manually installing the ALSA port). See my other emails regarding the procedure to build a wine- fbsd64 package. 3) File a bug report to bugs.winehq.org. I've found the sound guy very responsive and willing to fix the OSS backend (patches may be provided requiring parts of step 2). If you do not come right please ping me in the middle of Jan and I'll try assist you (I should be able to get a copy of CS 1.6). Regards, David signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.18 (32bit Wine for 64bit FreeBSD)
Hi, Apologies, the incorrect package was uploaded for wine-1.5.x-freebsd9 for wine-fbsd64-1.5.18. The correct file is: MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) = f256fb13adaf5c8bf313c5973ac8159c Regards, David On Saturday, 1 December 2012 15:21:14 David Naylor wrote: > Hi, > > Packages [1] for wine-fbsd64-1.5.18 have been uploaded to mediafire [2]. > The packages for FreeBSD 10 use the pkgng [3] format. > > Please read the installation messages, if you use the nVidia graphics > driver, for further information. > > FAQ > --- > Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: > Undefined symbol "_ThreadRuneLocale" > A: This problem is specific to FreeBSD-9.0, please either stick with > wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). > Apologies for the inconvenience. > > Q: Creating pkgng packages for FreeBSD-9 > A: When there is no demand for FreeBSD-8 packages I'll create additional > pkgng packages for FreeBSD-9. Since it is possible to install the > existing pkg packages in a pkgng environment (which I do) this is not a > high priority. > > Q: Wine doesn't run (properly) with a clang built world > A: Clang was compiling i386 on a 16-byte boundary while gcc was using a > 4-byte boundary. To fix, recompile world after ensuring your sources > include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant > MFC. > > Regards, > > David > > [1] > MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.18,1.tbz) = > 7335bcf8fd3a3bcb98a74e2b9d797963 > MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) = > 6fb7d760ffe9ef19457982e861e84f83 > MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.18,1.txz) = > 13c54f14d4f51e46f1b22320b41308ca > [2] http://www.mediafire.com/wine_fbsd64 > [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.20 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able to isolate where the problem is occurring (wine, ports, world, kernel, i386, amd64). A possible solution in to try upgrading, or downgrading, software used however I have not been able to fix the problem with my attempts. If you find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.20,1.tbz) = f292068a82cec3d068ce0ca6d154037c MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.20.1.txz) = 5467ea90a1ceac62f28eb4658cb53960 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.20,1.txz) = 6961696e9c8195b2969a46ee7ffa8a21 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.19 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.19 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able to isolate where the problem is occurring (wine, ports, world, kernel, i386, amd64). A possible solution in to try upgrading, or downgrading, software used however I have not been able to fix the problem with my attempts. If you find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.19,1.tbz) = c442808517aa6d77bb3c3d86f5a4031e MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.19.1.txz) = 86b2d231caba230d1829db1c961ed38c MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.19,1.txz) = 90b9aa6cc54024349ea5389efb7f9d4c [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.18 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.18 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.18,1.tbz) = 7335bcf8fd3a3bcb98a74e2b9d797963 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) = 6fb7d760ffe9ef19457982e861e84f83 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.18,1.txz) = 13c54f14d4f51e46f1b22320b41308ca [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.17 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.17 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-byte boundary. To fix, recompile world after ensuring your sources include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.17,1.tbz) = 54065bf41dbb28ecd2c90baf6f7bf9a1 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.17.1.txz) = 69b90dba97312cc5a8561c87d214e814 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.17,1.txz) = e040dc940bb6cfd821d10f086d78e72d [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Re: nvidia libs have an unrecognized owner (Was: Wine-fbsd64 updated to 1.5.16)
Hi,
Thanks for your report, I have amended the patch-nvidia.sh file per your
suggestions (see attached). It will be included in the next set of packages.
Regards
On Sunday, 28 October 2012 14:02:34 Jan Beich wrote:
> After running patch-nvidia.sh some files are left not owned by root.
>
> $ ls -l /usr/local/lib32/ | awk '$3 ~ /[[:digit:]]/ || $4 ~ /[[:digit:]]/'
> -rwxr-xr-x 1 2402 30 802148 Oct 9 18:30 libGL.so.1
> -rwxr-xr-x 1 2402 30 29200980 Oct 9 18:29 libnvidia-glcore.so.1
> -rwxr-xr-x 1 2402 30 3588 Oct 9 18:32 libnvidia-tls.so.1
>
> $ tar tvf /d/NVIDIA-FreeBSD-x86-310.14.tar.gz --include \*.so\*
> ...
> -rwxr-xr-x 0 buildmeister gopher 29200980 Oct 9 18:29
> NVIDIA-FreeBSD-x86-310.14/obj/libnvidia-glcore.so.1 -rwxr-xr-x 0
> buildmeister gopher 136392 Oct 9 18:33
> NVIDIA-FreeBSD-x86-310.14/obj/libnvidia-cfg.so.1 -rwxr-xr-x 0
> buildmeister gopher 802148 Oct 9 18:30
> NVIDIA-FreeBSD-x86-310.14/obj/libGL.so.1
>
> This is caused by tar(1) trying to preserve ownership/permissions when
> running under root by default. Here's how the ports tree handles it:
>
> EXTRACT_AFTER_ARGS?=| ${TAR} -xf - --no-same-owner --no-same-
permissions
>
> But wrong permissions are less noticeble there because install(1) with
> -o/-g/-m flags usually discards them anyway.
signature.asc
Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.16 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.16 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.16,1.tbz) = fae74f2dc33226f9c69d28b4dfb928b8 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.16.1.txz) = 467b906e0ec3ecca7f9441a02c69381c MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.16,1.txz) = 353f259b1820b9aeee6caf423a0b98e1 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.15 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.15 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. If you are having trouble with the FreeBSD-9 packages, please update to a newer version of FreeBSD. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.15,1.tbz) = 0e3f2bf82ed767c93924a048eb2945d5 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.15.1.txz) = 4cf6a54d40dd65e48dd0ee6aa736832d MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.15,1.txz) = 8fa11946ced1ef05d74489c74be16815 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.14 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.14 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.14,1.tbz) = 8f0c1c0a44616c52916f1f8da15cead8 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.14,1.txz) = 3464d06b9148e97ce75d908ef37693b1 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.14,1.txz) = 2c37f9354c74b2ed22cf2a8ae4886b0a [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On Sunday, 30 September 2012 19:14:37 Chuck Burns wrote: > On 09/30/2012 11:34 AM, David Naylor wrote: > > On Sunday, 30 September 2012 16:22:30 Chuck Burns wrote: > >> On 09/30/2012 09:06 AM, David Naylor wrote: > >>> The current pkg format can be installed along side a pkgng > >>> installation (the nvidia patching will detect the pkgng packages). Has > >>> this not worked on your setup? > >> > >> Yes, this works, I was hoping to be as "native" as possible. :) > > > > Doing so will increase my workload by 33% and I'm not willing to devote > > extra resources given that it currently works anyway. > > > > However, the usage of the FreeBSD-8 packages are low, so I may drop > > support for them and reconsider supporting pkgng for FreeBSD 9. It > > would also provide an interesting barometer for adoption of pkgng (I > > myself use it, except for wine packages, on FreeBSD-9). > > > > Regards > > How do you build this, anyway? I would love to be able to "cut out the > middle man" so to speak. I know the general idea is: build it in a > 32bit jail. But do you do it with a script? or just manually build the > packages? Since you asked ;-) ... I have a custom Makefile that manages my source files (for FreeBSD and Ports) and a script file that uses the Makefile to build the wine packages. The actual commands that I use are: # make -sj8 update ports # sh wine-fbsd.sh # env FBSD=freebsd8 sh wine-fbsd.sh # env FBSD=freebsd10 sh wine-fbsd.sh The script file is straight forward and the calls to `make -f /root/Makefile - j8 pkg-env ...` can be simply replaced with: # make -C /usr/src -sj8 world DESTDIR=$SCRATCHPAD to get the same effect. Note: /home/DragonSA/ports/wine-fbsd64.diff is the diff from mediafire. The Makefile is very specific to my setup, where I have a server that mirrors (using csup) FreeBSD 8, 9 and 10, and Ports, and I have /usr/ports and /usr/src as a symlink to /home/ports and /home/freebsd9/src respectively. I include it for completeness, if not for its actual usefulness. It shouldn't be difficult to create a script that is more general (maybe using portsnap [and svn export?] as cvs is being depreciated). If you do I will happily upload it to mediafire ;-) Regards signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On Sunday, 30 September 2012 16:22:30 Chuck Burns wrote: > On 09/30/2012 09:06 AM, David Naylor wrote: > > The current pkg format can be installed along side a pkgng > > installation (the nvidia patching will detect the pkgng packages). Has > > this not worked on your setup? > > Yes, this works, I was hoping to be as "native" as possible. :) Doing so will increase my workload by 33% and I'm not willing to devote extra resources given that it currently works anyway. However, the usage of the FreeBSD-8 packages are low, so I may drop support for them and reconsider supporting pkgng for FreeBSD 9. It would also provide an interesting barometer for adoption of pkgng (I myself use it, except for wine packages, on FreeBSD-9). Regards signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On Friday, 28 September 2012 17:58:05 Chuck Burns wrote: > On 9/24/2012 3:29 PM, David Naylor wrote: > > Hi, > > > > NOTICE: > > - fix: CUPS support should now work > > - fix: GNUTLS support should now work > > - CFT: with FreeBSD(-current) planning on switching to clang as default > > > > compiler (for world/kernel) could you please check if wine runs with a > > clang compiled world. Previous reports indicate wine (and libreoffice) > > didn't work with a clang libc however that may have been fixed. Please > > report for both success or failure and include `uname -a` and `clang > > --version`. Thanks > > > > Packages [1] for wine-fbsd64-1.5.13 have been uploaded to mediafire [2]. > > The packages for FreeBSD 10 use the pkgng [3] format. > > > > Please read the installation messages, if you use the nVidia graphics > > driver, for further information. > > > > Regards, > > > > David > > What is the possibility of a pkgng package for 9-stable, for those of us > already using/testing pkgng on our 9.x systems? The current pkg format can be installed along side a pkgng installation (the nvidia patching will detect the pkgng packages). Has this not worked on your setup? signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On Tuesday, 25 September 2012 21:59:35 Yuri wrote: > I experience this strange problem (1.5.13 is the only version I tried). > > I am trying to install python 2.6 using msi installer: > wine msiexec /i ~/python-2.6.msi > and this installs it into the current folder, not into c:/Python2.6 as > it should be. > > I ran the similar command (with various versions of python) many times. > First they were getting installed into the proper folder (under c:/). > But later msiexec stopped asking any questions and just drops all files > into the current folder. Same problem with other .msi installers. > > This might not be BSD specific. I am reporting it because this is a > failure of a basic command that many are likely to run. > > In addition texts in window displayed by msiexec have messed up > characters (wrong fonts?). Not sure why, but I see this across many > programs ran by wine, digitaleditions would be another example. Hi Yuri, I just tried with a clean wine prefix with python-2.7.3.msi and everything works as expected. Given that the fonts are also broken it may be your prefix or installation is somehow broken. You could try: # env WINEPREFIX=/tmp/python wine msiexec /i ~/python-2.6.msi to check if it is your prefix that is broken. Failing that try reinstalling the wine package (and check the checksum). Good luck, Regards, David signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
Hi, NOTICE: - fix: CUPS support should now work - fix: GNUTLS support should now work - CFT: with FreeBSD(-current) planning on switching to clang as default compiler (for world/kernel) could you please check if wine runs with a clang compiled world. Previous reports indicate wine (and libreoffice) didn't work with a clang libc however that may have been fixed. Please report for both success or failure and include `uname -a` and `clang --version`. Thanks Packages [1] for wine-fbsd64-1.5.13 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.13,1.tbz) = fa31279a464b3ddb0074467899c3b57d MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.13,1.txz) = ff19bfbc987560fd8685879210c0bb5c MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.13,1.txz) = 6752cf8b20956e29910b2cf1fa3e3509 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Re: wine && libgnutls
On Saturday, 15 September 2012 11:33:35 Matthias Apitz wrote: > Hello, Hi > I must use wine(1) to run some Adobe Digital Editions tool (which seems > to work fine with wine in general, the wine pages say it runs); > > When I start: > > $ wine digitaleditions_172.exe > > it can't find some shared lib for TLS: > > err:secur32:SECUR32_initSchannelSP libgnutls not found, SSL connections > will fail If the below does not work, please do: # env WINEDEBUG=all wine digitaleditions_172.exe To get more detailed messages (be selective with what you post). > I have: > > $ uname -a > 9.0-CURRENT #1 r21: Thu Oct 28 10:56:32 CEST 2010 This is an incomplete `uname`. Of interest that is missing is your architecture, which I am assuming is i386? > $ pkg_info | egrep 'wine|gnutls' > gnutls-2.8.6_2 GNU Transport Layer Security library > wine-1.3.6,1Microsoft Windows compatibility layer for Unix-like > systems > > Any idea why wine(1) can't see the gnutls lib? Thanks Are you using a package or did you compile from ports, also the version of wine you are using is outdated. Please consider updating to either emulators/wine or emulators/wine-devel. Wine needs to be compiled with gnutls support, please (re)build the wine port, ensuring the GNUTLS optioin is on. Regards signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.12 (32bit Wine for 64bit FreeBSD)
On Sunday, 2 September 2012 07:37:34 alphachi wrote: > 2012/9/1 David Naylor > > > Hi, > > > > Packages [1] for wine-fbsd64-1.5.12 have been uploaded to mediafire [2]. > > > > The > > > > packages for FreeBSD 10 use the pkgng [3] format. > > > > There are many reports that wine does not work with a clang compiled > > world (help in fixing this problem is appreciated as it affects quite a > > few users). > > > > The patch [4] for nVidia users is now included in the package and is run > > on installation (if the relevant files are accessible). Please read the > > installation messages for further information. > > > > Regards, > > > > David > > > > [1] > > > > MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.12,1.tbz) = > > > > 335ef444a2f6f375dd22cf932b651919 > > > > MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.12,1.txz) = > > > > e06673c4ab9a0bb82a7d48dad5b8877f > > > > MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.12,1.txz) = > > > > aafe06b15176f810c25cbf708c11aabb > > > > [2] http://www.mediafire.com/wine_fbsd64 > > [3] http://wiki.freebsd.org/pkgng > > [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh > > Hi David, Hi > I have pkg_add wine-fbsd64-1.5.12,1.txz and run > /usr/local/share/wine/patch- nvidia.sh; everything is OK. > > When running wine, the error msg is: > wine: failed to initialize: /usr/local/lib32/wine/ntdll.dll.so: Undefined > symbol "_ThreadRuneLocale" > > What shall I do? Thanks! Could you please answer some questions: - Are you running FreeBSD 9 or 10? - When last did you update world? - Are you using clang for any compilation (of world, ports, etc) - How did you run wine? Could please run the followings commands, and provide the output: # uname -a # winecfg # regedit also please run the program that tripped wine up. Some things you could try [the following long shots] (although I have no idea what the root cause is til I get further information): - Have a look at http://markmail.org/thread/5kt24py6q2w2ageq - Update to the latest -stable or -current code - If you were using clang then switch to gcc and do a full rebuild Regards signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.12 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.12 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.12,1.tbz) = 335ef444a2f6f375dd22cf932b651919 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.12,1.txz) = e06673c4ab9a0bb82a7d48dad5b8877f MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.12,1.txz) = aafe06b15176f810c25cbf708c11aabb [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.11 (32bit Wine for 64bit FreeBSD)
4Hi, Packages [1] for wine-fbsd64-1.5.11 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.11,1.tbz) = 6ef223d508e191c18ed9fa92b993cd4c MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.11,1.txz) = 81f373343dc765b226710aff43206991 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.11,1.txz) = 9159e7ac79283dd146084633a56af34d [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.10 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.10 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.10,1.tbz) = cb4bf5e3247ae60e5869241b6db80edf MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.10,1.txz) = bbe24a80cb14c4a0c0acf3f259298137 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.10,1.txz) = 76f0832e95c107cb1d4ac1eacacb2d6a [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.9 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.9 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.9,1.tbz) = dddaceda7c0dedd03e5f8531d9826966 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.9,1.txz) = aec8afccdd6ac6928662d3be5f537195 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.9,1.txz) = 9436b443844ac8bf52d9ead2de55cf33 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh * pkgng support for nVidia patching should be working properly and using a mixed mode between pkgng and pkg also works signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.8 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.8 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.8,1.tbz) = bc57b6b573816d24837c9171e38cdfaf MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.8,1.txz) = 4c06fd3e68c43c977449ab9f824f69dd MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.8,1.txz) = 34cce0d89ef9d3db47f7699a3769a6cd [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh * pkgng support for nVidia patching should be working properly and using a mixed mode between pkgng and pkg also works signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.7 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.7 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.7,1.tbz) = 0178e90ad6cdcdf61d22324c8ccdeab5 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.7,1.txz) = c658144284981dbc1543365f7d644534 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.7,1.txz) = 921a5a114cc4feb75446ff491168dca5 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh * pkgng support for nVidia patching should be working properly and using a mixed mode between pkgng and pkg also works signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.6 (32bit Wine for 64bit FreeBSD)
On Friday, 22 June 2012 12:26:50 Jan Beich wrote:
> (ports@ folk may know more about pkgng)
>
> David Naylor writes:
> > Hi,
> >
> > Packages [1] for wine-fbsd64-1.5.6 have been uploaded to mediafire [2].
> > The packages for FreeBSD 10 use the pkgng* [3] format.
>
> [...]
>
> > * Support for pkgng has been added to the nvidia-patch script
>
> pkgng seems to be more pedantic regarding conflicting files. And I
> haven't found a way to force register a package.
I have reported this issue to both pkgng and FreeBSD ports. I managed to get
it to register by tweaking pkg-plist, also not defining WITH_PKGNG may work
(and with the changes to nvidia.sh it will fall back to `pkg_info` if `pkg
info` doesn\t yield).
> --- patch-nvidia.sh~
> +++ patch-nvidia.sh
> @@ -92,12 +92,20 @@ do
> done
>
> version() {
> + local ret pkg="$1"
>if [ -f "/usr/local/sbin/pkg" ]
>then
> -echo `pkg query -g '%v' $1`
> +ret=`pkg query -g '%v' $pkg`
>else
> -echo `pkg_info -E $1'*' | cut -f 3 -d -`
> +ret=`pkg_info -E $pkg'*' | cut -f 3 -d -`
>fi
> + # installed manually or failed to register
> + if [ -z "$ret" ] && [ "$pkg" = "nvidia-driver" ]
> + then
> +ret=`sed 2>/dev/null -n 's/.*Version: //p' \
> + $PREFIX/share/doc/NVIDIA_GLX-1.0/README || true`
> + fi
> + echo "$ret"
> }
>
> [ `whoami` = root ] \
Thanks for your patch. I have updates the nvidia.sh script and given you
credit. This will be available from wine 1.5.7.
Regards
signature.asc
Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.4.1 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4.1 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.4.x-freebsd8/wine-fbsd64-1.4.1,1.tbz) = 63f031c996b1201b056db34e6aa5b8f3 MD5 (wine-1.4.x-freebsd9/wine-fbsd64-1.4.1,1.txz) = 86aa9c66f05c61def997076befac5ba3 MD5 (wine-1.4.x-freebsd10/wine-fbsd64-1.4.1,1.txz) = b0b19714510f278187dcf8c696cae9c0 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.6 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.6 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.6,1.tbz) = 5a89d8cd18c65c6f27a565e78598ebd8 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.6,1.txz) = 0992a7d5bf73759f8a8f97ae793c6eee MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.6,1.txz) = 2f807a63ff2f8d8833b4b89846e5e68a [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh * Support for pkgng has been added to the nvidia-patch script signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.5 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.5 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.5,1.tbz) = 2f4b826306dfe7feed396a4752df87ca MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.5,1.txz) = ff8ef2a3678ae1c6f28bb376f9996c06 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.5,1.txz) = e53ed61cc5ce5d046f8ae31363b8ef2d [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh [*] The pkgng packages are now labelled for FreeBSD 64bit by default signature.asc Description: This is a digitally signed message part.
FreeBSD and Diablo III (partial solved)
Hi All, The following instructions allows one to play Diablo III under either i386 or amd64 FreeBSD 9. Unfortunately actually installing the game does not work due to problems with Agent.exe however once installed (from a Windows instance) the game runs well, with 48 hours reported as error free. Special thanks to alphachi for solving and testing the below procedure. Instructions: 1) Install the wine-fbsd64-diablo3[1] package from mediafire[2] (tested using 1.5.4). 2) Choose a directory to have the diablo 3 wine prefix (`export DIABLO=$HOME/diablo3` or `setenv DIABLO $HOME/diablo3`) 3) Install VC++ 2008 Redistribution (`env WINEPREFIX=$DIABLO sh winetricks vcrun2008`)[3] 4) Copy an INSTALLED version of diablo 3 to the wine prefix (hint: use VirtualBox to install the game) 5) Start the game with `env WINEPREFIX=$DIABLO wine Diablo\ III.exe -launch` [4] Regards, [1] MD5 (wine-1.4.x-freebsd9/wine-fbsd64-diablo3-1.4,1.tbz) = 9d327d7cc384cce7317e7c70245b9427 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-diablo3-1.5.4,1.txz) = 250d424f14fa9670396addaaaed8c43e [2] http://www.mediafire.com/wine_fbsd64 [3] http://winetricks.org/winetricks [4] Below is a sample .desktop file for launching diablo 3. Please expand $DIABLO and fix the "Path" entry [Desktop Entry] Comment=Please replace $DIABLO with a full expanded path and fix "Path" entry Exec=env WINEPREFIX=$DIABLO wine "Diablo III.exe" -launch Name=Diablo III Path=$DIABLO/drive_c/path/to/diablo StartupNotify=true Terminal=false TerminalOptions= Type=Application signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.4 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.4 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.4,1.tbz) = 4fe4310bb941cb151c3d9cba719342db MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.4,1.txz) = 6f224419362e1c75ce7fc799e3038b00 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.4,1.txz) = fdb9db7a3d54daa9c9437d813b01592c [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh [*] To install the port first fix the arch tag use the 'fix-arch.sh' script from mediafire [2] signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
On Monday, 7 May 2012 18:09:29 fidaj wrote: > --- Оригінальне повідомлення --- > Від кого: "David Naylor" > Кому: freebsd-emulation@freebsd.org, freebsd-questi...@freebsd.org > Дата: 7 травня 2012, 11:45:18 > Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD) > > root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz > tar: +CONTENTS: Not found in archive > tar: Error exit delayed from previous errors. > pkg_add: tar extract of > /home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed! > pkg_add: unable to extract table of contents file from > '/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a package? > > md5 > > wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz > > MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 To install wine-fbsd64 on FreeBSD 10 please do: # make -C /usr/ports/ports-mgmt/pkg install clean # sh fix-arch.sh wine-fbsd64-1.5.3,1.txz # pkg add wine-fbsd64-1.5.3,1.txz fix-arch.sh is available from mediafire. Regards signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.3 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.3,1.tbz) = 0592e0b1226314a7061ef5745fa0e59f MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.3,1.txz) = 002e343a7bcb0cea7456422b75aec8f6 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh [*] To install the port first fix the arch tag use the 'fix-arch.sh' script from mediafire [2] signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.2 (32bit Wine for 64bit FreeBSD)
On Friday, 20 April 2012 09:18:59 David Naylor wrote: > On Thursday, 19 April 2012 12:05:53 Jan Beich wrote: > > wmc/wrc depend on devel/gettext, while the lib is missing in the package. > > I have confirmed this. > > > $ wmc > > Shared object "libgettextpo.so.5" not found, required by "wmc" > > Exit 1 > > > > $ readelf -d /usr/local/bin32/wrc | fgrep -i library > > > >0x0001 (NEEDED) Shared library: > > [libgettextpo.so.5] 0x0001 (NEEDED) Shared > > library: [libwine.so.1] 0x0001 (NEEDED) Shared > > library: [libc.so.7] 0x000f (RPATH) Library > > rpath: [$ORIGIN/../lib32] 0x001d (RUNPATH)Library > > runpath: [$ORIGIN/../lib32] > > > > $ tar tf wine-fbsd64-1.5.2,1.txz | fgrep gettext > > Exit 1 > > > > Why? (for the archives) > > The port uses a script to determine which files need to be added into the > package. I suspect it is not inspecting the bin32 directory and thus > missing those files. The script added the bin32/* paths after the search for dependencies. Moving that code above the search fixes the problem. I have uploaded updated patches and unless anyone needs a fix for wine-fbsd64-1.5.2,1 then I'll fix it for the next release? Regards signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.2 (32bit Wine for 64bit FreeBSD)
On Thursday, 19 April 2012 12:05:53 Jan Beich wrote: > wmc/wrc depend on devel/gettext, while the lib is missing in the package. I have confirmed this. > $ wmc > Shared object "libgettextpo.so.5" not found, required by "wmc" > Exit 1 > > $ readelf -d /usr/local/bin32/wrc | fgrep -i library >0x0001 (NEEDED) Shared library: > [libgettextpo.so.5] 0x0001 (NEEDED) Shared > library: [libwine.so.1] 0x0001 (NEEDED) Shared > library: [libc.so.7] 0x000f (RPATH) Library > rpath: [$ORIGIN/../lib32] 0x001d (RUNPATH)Library > runpath: [$ORIGIN/../lib32] > > $ tar tf wine-fbsd64-1.5.2,1.txz | fgrep gettext > Exit 1 > > Why? (for the archives) The port uses a script to determine which files need to be added into the package. I suspect it is not inspecting the bin32 directory and thus missing those files. I'll look into it. Thanks for your report. David signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.2 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.1 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.2,1.tbz) = b5fb7ac0fb6a5ba01863a3f1502f8c23 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.2,1.txz) = 592bfb92be8aad9e681070cda89944e9 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.2,1.txz) = 58ef0cb5c0b090de4e52bde8f78b5252 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.1 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.1 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.1,1.tbz) = f8e1c24fc18dea444aed84b4bde8db25 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.1,1.txz) = 05a2c1baed81108041fa650a6ee0d78a [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.5.0 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.0 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.4,1.tbz) = 0f6e1481ffc40e6f15df01893c632bcc MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.4,1.txz) = 68dcb36632f2ed7498316544db5c7abc [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.4 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.4,1.tbz) = fad0512004281ab610544e1daa0ab495 MD5 (freebsd9/wine-fbsd64-1.4,1.txz) = aeccf8a14f0ff29bd956c39911eb8fec [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)
On Tuesday, 6 March 2012 00:01:48 Mehmet Erol Sanliturk wrote: > On Mon, Mar 5, 2012 at 3:00 PM, David Naylor wrote: > > On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote: > > > On Mon, Mar 5, 2012 at 6:55 AM, David Naylor > > > > wrote: > > > > Please include the full error message, also could you please try > > > > running > > > > > > those apps in a clean wine prefix. > > > > > > # pwd > > > /root/APPLY/PROGRAMS > > > > > > # wine x.exe > > > > > > err : module : LdrInitializeThunk Main exe initialization for > > > L"F:\\APPLY\\PROGRAMS\\x.exe" failed , status c017 > > > > I have tried to reproduce the error on my side but was unable to. The > > programs that I tested work without error. > > This means that there are additional parts in your system which they do not > exist here . > Such parts are not added by "pkg_add wine-fbsd64 ..." . > I do not have any idea about which parts may be missing . It could also mean there are extra components on your computer that are interfering however using a clean wine prefix (as mentioned below) has ruled that out. > > I was expecting more output from wine... Please see below about using a > > clean > > wine prefix. Do you use the nvidia graphics driver? If so please run > > (as root), and provide the output: > > # sh /usr/local/share/wine/patch-nvidia.sh > > There is NO nvidia grphics driver . It is Intel DG965WH main board with its > integrated graphics driver . That eliminates my only other idea. > > If nothing fixes your problem then please submit a bug report at > > bugs.winehq.org. > > > > > I could not understand the phrase : > > > > > > "in a clean wine prefix" . > > > > To run a program in a clean wine prefix do: > > env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe > > This is NOT changing the error message . Only drive become Z: . As mentioned above, eliminates possible extra components causing interference. > > You may need to use winetricks to install some support programs. > > > > Good luck > > "winetricks" could NOT be found . Please see http://wiki.winehq.org/winetricks for details about winetricks. > I tried wine which is added by > > pkg_add -r wine > > from packages > > in FreeBSD 9.0 RELEASE i386 as it is installed . > > On the same programs , the message is the same with amd64 message . To clarify: you tried running the program under an i386 installation of FreeBSD and wine gave you the same problem? Also, has a previous version of wine ever worked for your program? Could you try installing an older version of wine (the mediafire page contains wine releases going back to 1.3.16). Regards signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)
On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote: > On Mon, Mar 5, 2012 at 6:55 AM, David Naylor wrote: > > Please include the full error message, also could you please try running > > those apps in a clean wine prefix. > > # pwd > /root/APPLY/PROGRAMS > > # wine x.exe > > err : module : LdrInitializeThunk Main exe initialization for > L"F:\\APPLY\\PROGRAMS\\x.exe" failed , status c017 I have tried to reproduce the error on my side but was unable to. The programs that I tested work without error. I was expecting more output from wine... Please see below about using a clean wine prefix. Do you use the nvidia graphics driver? If so please run (as root), and provide the output: # sh /usr/local/share/wine/patch-nvidia.sh If nothing fixes your problem then please submit a bug report at bugs.winehq.org. > I could not understand the phrase : > > "in a clean wine prefix" . To run a program in a clean wine prefix do: env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe You may need to use winetricks to install some support programs. Good luck signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)
On 5 March 2012 13:41, Mehmet Erol Sanliturk wrote: > On Sun, Mar 4, 2012 at 2:16 PM, David Naylor > wrote: >> >> Hi, >> >> Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire [2]. >> >> There are many reports that wine does not work with a clang compiled world >> (help in fixing this problem is appreciated as it affects quite a few >> users). >> >> The patch [3] for nVidia users is now included in the package and is run >> on >> installation (if the relevant files are accessible). Please read the >> installation messages for further information. >> >> Regards, >> >> David >> >> [1] >> MD5 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) = >> 91bc2288130c25704c9f1ac9d2923a6a >> MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) = >> a57b6fed2401375562931f3516e1d50b >> [2] http://www.mediafire.com/wine_fbsd64 >> [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh > > > > For any x.exe : > > wine x.exe > > is generating the following error : > > err: module : LdrInitializeThunk Main exe initialization for L"F:\\ ... path > ... \\x.exe" failed , > status c017 Please include the full error message, also could you please try running those apps in a clean wine prefix. > where x.exe is in the current directory ( path is correct ) > > in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64 I will try reproduce this when I get $HOME. Regards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) = 91bc2288130c25704c9f1ac9d2923a6a MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) = a57b6fed2401375562931f3516e1d50b [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.4.rc5 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4.rc5 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.4.rc5,1.tbz) = 53c37ef9fbd0f12f6c456efac942a575 MD5 (freebsd9/wine-fbsd64-1.4.rc5,1.txz) = 4f653f5d8e29fd5e7811dec2f81469a8 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.4.rc4 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4.rc4 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.4.rc4,1.tbz) = aa6a8af686c8df34d14ccfaa8d8f2f9e MD5 (freebsd9/wine-fbsd64-1.4.rc4,1.txz) = 582b3b70cfb77008d753e676cdef52e2 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.4.rc3 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4.rc3 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.4.rc3,1.tbz) = 0a63374ea1f14c205a49d189acba8015 MD5 (freebsd9/wine-fbsd64-1.4.rc3,1.txz) = 02362559af1efe9088c7aa3adc6c4da4 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Wine-fbsd64 updated to 1.4.rc2 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.4.rc2 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.4.rc2,1.tbz) = 81276c61d8f120070c169b9dfb3b8856 MD5 (freebsd9/wine-fbsd64-1.4.rc2,1.txz) = ac312c16b63e7d3b4847b092c9b47720 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.37 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.37 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.37,1.tbz) = 5e1db52bca7de4e5b6db2705eeff21f3 MD5 (freebsd9/wine-fbsd64-1.3.37,1.txz) = e9ebe02bda0b5d81667df69c23c1dc3f [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD)
On Monday, 9 January 2012 20:19:48 Chuck Burns wrote: > On 01/09/12 12:17, David Naylor wrote: > > Hi, > > > > Packages [1] for wine-fbsd64-1.3.36 have been uploaded to mediafire [2]. > > > > There are many reports that wine does not work with a clang compiled > > world (help in fixing this problem is appreciated as it affects quite a > > few users). > > > > The patch [3] for nVidia users is now included in the package and is run > > on installation (if the relevant files are accessable). Please read the > > installation messages for further information. > > > > Regards, > > > > David > > > > [1] > > > >MD5 (freebsd8/wine-fbsd64-1.3.36,1.tbz) = > >019cdde0ff7fad7dc877ed1e3bc3c481 MD5 > >(freebsd9/wine-fbsd64-1.3.36,1.txz) = > >7fe1bbd75c8c6af1d3fe6f0a03841fa2 > > > > [2] http://www.mediafire.com/wine_fbsd64 > > [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh > > Have you put any thought into getting both wine and wine64 (for Wow64 > apps) working? There have been more than a few people hopping onto IRC > asking about wine64 (full 64bit wine) I wasn't aware of WoW64 (and how it will make my packages redundent :->). I see there are two wiki pages: + http://wiki.winehq.org/Wine64 + http://wiki.winehq.org/Wine64ForPackagers The latter makes this statement "Wine 64bit works at the moment only on Linux." which would indicate that, at this stage, FreeBSD is precluded. That, however, is just my speculation. To answer your question directly, I have put no thought or effort into wine64. signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.36 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.36,1.tbz) = 019cdde0ff7fad7dc877ed1e3bc3c481 MD5 (freebsd9/wine-fbsd64-1.3.36,1.txz) = 7fe1bbd75c8c6af1d3fe6f0a03841fa2 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.35 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.35 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.35,1.tbz) = 4e8daf48015fa8036ffb917fd7ff2c07 MD5 (freebsd9/wine-fbsd64-1.3.35,1.txz) = 996447cf4267e3070ab0cd8208647b14 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.34 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.34 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.34,1.tbz) = 772fc62a7278f9838b273b04c64aba00 MD5 (freebsd9/wine-fbsd64-1.3.34,1.txz) = b8267c46e9dc6727f23138ec146abf68 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.33 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.33 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.33,1.tbz) = a3eb5e2b32b8c7fa91e67aecee1cc197 MD5 (freebsd9/wine-fbsd64-1.3.33,1.txz) = 0a1b483fc8ee107653586aa56d464814 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.32 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.32 have been uploaded to mediafire [2]. These packages include the patch (first version) from bug report 27653 (http://bugs.winehq.org/show_bug.cgi?id=27653). This fixes logging in for EVE Online. There is a known UDP related problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for details). Also, there are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.32,1.tbz) = 4e05528f6e26004b4bcd3e1dafb5e821 MD5 (freebsd9/wine-fbsd64-1.3.32,1.txz) = 7951f88480723aee516fe211ad5a6950 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)
Hi, I have fixed an issue where the integrated nVidia patch failed to install or run as expected. The packages [4] have been uploaded and replaced the old packages. Only if you are a nVidia user who has been unable to get wine-1.3.31 working would you need to download and install the updated packages. Lastly, there are reports that wine does not work with a clang built world. Regards, David [4] MD5 (freebsd8/wine-fbsd64-1.3.31,1.tbz) = e38e694dc55a99882c137d0f11b4eb9e MD5 (freebsd9/wine-fbsd64-1.3.31,1.txz) = 59ec8c1b68e3eb12f4b2c97674d0d563 On Tuesday, 25 October 2011 18:52:40 David Naylor wrote: > Hi, > > Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and > the wine-fbsd64.diff patch has been updated. There is a known UDP related > problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for > details). > > To date there has been 1217 (+70) downloads from mediafire. > > The patch [3] for nVidia users is now included in the package and is run on > installation (if the relevant files are accessable). Please read the > installation messages for further information. > > Regards, > > David > [1] > MD5 (freebsd8/wine-fbsd64-1.3.31,1.tbz) = > 3ada791cc70a692b71f331a9b658d0ce MD5 (freebsd9/wine-fbsd64-1.3.31,1.txz) = > 7b9f0b9a122646822542e540aeed09e5 [2] http://www.mediafire.com/wine_fbsd64 > [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)
Hi Romain, Thank you for the report. I will address this over the coming week and update the packages. In the interim, the packages will work for both nvidia and non-nvidia users except nvidia users will need to run patch-nvidia-wine.sh (from mediafire) manually... Regards On 30 October 2011 13:07, Romain Garbage wrote: > 2011/10/25 David Naylor : >> Hi, > > Hi, > >> Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and >> the wine-fbsd64.diff patch has been updated. There is a known UDP related >> problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for >> details). >> >> To date there has been 1217 (+70) downloads from mediafire. >> >> The patch [3] for nVidia users is now included in the package and is run on >> installation (if the relevant files are accessable). Please read the >> installation messages for further information. > > $ sudo pkg_add Downloads/wine-fbsd64-1.3.31,1.txz > tar: /usr/local/share/wine/patch-nvidia.sh: Cannot stat: No such file > or directory > tar: Error exit delayed from previous errors. > A NVIDIA GRAPHICS DRIVER HAS BEEN DETECTED ON THIS SYSTEM AND THE AUTOMATED > PATCHING HAS FAILED, execute (as root) > sh /usr/local/share/wine/patch-nvidia.sh > to get 2D/3D acceleration to work with the nvidia driver. Without this wine > will crash when a program requires 2D/3D graphics acceleration. > [...] > > $ file /usr/local/share/wine/patch-nvidia.sh > /usr/local/share/wine/patch-nvidia.sh: cannot open > `/usr/local/share/wine/patch-nvidia.sh' (No such file or directory) > > $ tar tf Downloads/wine-fbsd64-1.3.31,1.txz | grep -C 2 nvidia > bin32/wmc > bin32/wrc > usr/local/share/wine/patch-nvidia.sh > share/wine/fonts/coue1255.fon > share/wine/fonts/coue1256.fon > > The problem here seems to be the trailing usr/local/ for > patch-nvidia.sh file, which get actually installed into > $PREFIX/usr/local/share/wine instead of $PREFIX/share/wine > > Regards, > Romain > > PD: I used the fbsd9 package. md5 is ok. > ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and the wine-fbsd64.diff patch has been updated. There is a known UDP related problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for details). To date there has been 1217 (+70) downloads from mediafire. The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.31,1.tbz) = 3ada791cc70a692b71f331a9b658d0ce MD5 (freebsd9/wine-fbsd64-1.3.31,1.txz) = 7b9f0b9a122646822542e540aeed09e5 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.30 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.30 have been uploaded to mediafire [2]. To date there has been 1147 (+28) downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.30,1.tbz) = 9595e0991d8e9a9c10d6111f1d508c21 MD5 (freebsd9/wine-fbsd64-1.3.30,1.txz) = 3aa8bf39a6ad49c6060e9ca7b3c64d0d [2] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.29 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.29 have been uploaded to mediafire [2]. To date there has been 1119 (+183) downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.29,1.tbz) = 3c5d8896352dc16a829c045dc52c1f2e MD5 (freebsd9/wine-fbsd64-1.3.29,1.txz) = db2855755650c300135c50ed8361cbb9 [2] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.28 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.28 have been uploaded to mediafire [2]. This does contain XInput2 support. The sound issues appear to be resolved. If you experience any sound issues please report them to bugs.winehq.org and CC me. To date there has been 936 (+14) downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.28,1.tbz) = 4b9beb95ff38879320b69482598a96da MD5 (freebsd9/wine-fbsd64-1.3.28,1.txz) = 9f5cb96d937eeafd349965f98c543b80 [2] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Re: WINE sound failing in StarCraft II
Hi, On Tuesday, 30 August 2011 21:08:13 Richard Kolkovich wrote: > Hi. I'm just setting up my new laptop (9.0-BETA1/amd64 - building WINE > in a 32-bit chroot), and I am experiencing the issue reported > previously here: > > http://lists.freebsd.org/pipermail/freebsd-emulation/2011-July/009007.html > > The sound test works fine in winecfg, but there is no sound when > launching SC2. My soon-to-be-decommissioned desktop works fine with > the same setup under WINE 1.3.25. Both machines have Intel sound > cards, and the default devices are NOT mixer/dsp0. The output on the > laptop shows it is accessing the proper device, though (dsp2.vp0). > > Does anyone have any insight as to how to fix this? I don't have > anything else installed via WINE to see if this is specific to SC2, > but I can try that later, given some time. I am experiencing a similar sound problem. I have many games whos sound does work except one that has no sound. On solution is to switch to a version of wine prior to 1.3.25 (I found 1.3.23 the best) and to reinstall the game in a clean prefix. For me it appears wine 1.3.25 (and above) do something with the settings that prevent previous versions of wine from working properly. See bugzilla [1] for the bug I reported and mediafire [2] for precompiled wine packages that workd under FreeBSD/amd64. Regards [1] http://bugs.winehq.org/show_bug.cgi?id=28212 [2] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.27 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.27 have been uploaded to mediafire [2]. This does contain XInput2 support. There are still reports of sound problems. To date there has been 920 (+62) downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.27,1.tbz) = 03e3ecdd363ac0f343ba90eb8ef2ec2a MD5 (freebsd9/wine-fbsd64-1.3.27,1.txz) = ef790879eb2e8cf823cc7cd874afabed [2] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.26 (32bit Wine for 64bit FreeBSD)
Hi, Packages for wine-fbsd64-1.3.26 have been uploaded to mediafire [1]. This does contain XInput2 support. There are still reports of sound problems. To date there has been 858 (+173) downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.3.25 (32bit Wine for 64bit FreeBSD)
On Saturday, 30 July 2011 21:33:23 Mickaël Maillot wrote: > 2011/7/28 David Naylor > > > There is an incomplete (but should be more than sufficient) kernel patch, > > see > > kern/159236 and a patch at > > http://bugs.winehq.org/show_bug.cgi?id=27917that fixes wine (if you want > > to build wine-fbsd64, or normal wine). > > ok so i just copied the patch in emulation/wine/files/ folder > http://fneu.fr/freebsd/patch-dlls__wineoss.drv__mmdevdrv.c > and the sound works in winecfg. > > i still have no sound in Starcraft 2 with the following error: > err:oss:AUDDRV_GetAudioEndpoint Unable to open device /dev/dsp4.vp0: 16 > (Device busy) > i will try to find why this week end if i have some free time. Try changing the hardware acceleration from emulation to full. That fixes a problem for me. Also the audio developers at wine are very responsive to bug reports. If you have the time please report this bug (even if changing hardware acceleration fixes it) and attach the output of wine with WINEDEBUG="+tid, +dsound,+winmm,+mmdevapi,+oss,+alsa,+coreaudio" environ variable set. Good hunting signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.3.25 (32bit Wine for 64bit FreeBSD)
On Thursday, 28 July 2011 19:00:53 Mickaël Maillot wrote: > 2011/7/24 David Naylor > > > Hi, > > > > Packages for wine-fbsd64-1.3.25 have been uploaded to mediafire [1]. > > This does contain XInput2 support (whereas wine-fbsd64-1.3.24 does not). > > There are > > reports of sound problems. > > Hi, > > first, thanks for your work ! > and any tricks for the sound problem or we have to wait some oss fix ? There is an incomplete (but should be more than sufficient) kernel patch, see kern/159236 and a patch at http://bugs.winehq.org/show_bug.cgi?id=27917 that fixes wine (if you want to build wine-fbsd64, or normal wine). I am experiencing some further sound problems with some games but I am leaving that investigation for 1.3.26. Please let me know if none of the above solutions do not work for you... signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.25 (32bit Wine for 64bit FreeBSD)
Hi, Packages for wine-fbsd64-1.3.25 have been uploaded to mediafire [1]. This does contain XInput2 support (whereas wine-fbsd64-1.3.24 does not). There are reports of sound problems. To date there has been 685 downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.24 (32bit Wine for 64bit FreeBSD)
Hi, Packages for wine-fbsd64-1.3.24 have been uploaded to mediafire [1]. This does not contain XInput2 support (whereas wine-fbsd64-1.3.23 does). To date there has been 609 downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Wine-fbsd64 updated to 1.3.22 (32bit Wine for 64bit FreeBSD)
Hi, Packages for wine-fbsd64-1.3.22 have been uploaded to mediafire [1]. This is for those who experience regressions with wine-fbsd64-1.3.23, wine-fbsd64-1.3.24 will be forthcoming... To date there has been 606 downloads from mediafire. nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] http://www.mediafire.com/wine_fbsd64 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Wine-fbsd64 updated to 1.3.23 (32bit Wine for 64bit FreeBSD)
Hi, Packages for wine-fbsd64-1.3.23 have been uploaded to mediafire [1]. The package now contains support for XInput2, fixing mouse warp, and is based on PR ports/158406. This release fixes installation of MS Office 2007 compared to 1.3.21 (previous package available). nVidia uses should rerun patch-wine-nvidia.sh after updating wine. Regards, David [1] http://www.mediafire.com/wine_fbsd64 signature.asc Description: This is a digitally signed message part.
Re: wine64
On Wednesday 22 June 2011 02:30:25 Rusty Nejdl wrote: > On Tue, 21 Jun 2011 14:09:41 -1000, Bruce Meier wrote: > > Hi all, > > > > I downloaded wine-fbsd64-1.3.21,1.tbz from > > http://www.mediafire.com/wine_fbsd64 and it > > installed without a problem. However when I run it I get the > > > > following error: > > "ELF interpreter /libexec/ld-elf.so.1 not found Abort". > > > > I installed on an amd64 using freebsd-8.2. > > Can anyone help? > > > > Thanks, > > Bruce > > Bruce, > > I'm not sure if anyone on this list represents the quality of that > file. For the record, I am the maintainer of those ports. Bruce: did you sort out the problem? signature.asc Description: This is a digitally signed message part.
Re: Wine on amd64?
On Saturday 02 October 2010 19:27:54 Fernando Apesteguía wrote: > On Sat, Oct 2, 2010 at 6:01 PM, Sergey Nikolenko wrote: > > On 02.10.2010 21:25, Scott Ballantyne wrote: > >> Hi there, > >> > >> I'm interested in trying wine. I use the FBSD-8.1 amd64 platform. I > >> found some emails from January 2010 that imply you need to build this > >> on i386, but I have no access to an i386 machine, and there is no wine > >> in the amd64 packages. > >> > >> Can anyone update me on the status of Wine for amd64, and perhaps help > >> me find a pre-compiled version? > > > > Take a look at this: > > > > http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6 > > d http://people.freebsd.org/~ivoras/wine/ > > For what it is worth, I tried the precompiled provided by Ivan Voras > to run mainly Spotify and it works like a charm. There are updated packages at http://drop.io/wine_fbsd64 . I will be updating the packages to 1.3.4 over the next few days. Regards signature.asc Description: This is a digitally signed message part.
Re: sc2 with wine on amd64
On Sunday 11 July 2010 17:11:30 Mickaël Maillot wrote: > i disable nx protection in my BIOS and no change. Have you been successful in running this game under FreeBSD/i386? I have been experiencing a few applications that do not enjoy running under wine/i386 and FreeBSD/amd64. Since I no longer run i386 systems I do not know if this is a result of wine or FreeBSD. > 2010/7/11 David Naylor : > > On Sunday 11 July 2010 12:17:23 Mickaël Maillot wrote: > >> Hi > >> > >> i try to play StarCraft 2 with wine on my amd64 8-STABLE desktop. > >> first there is a patch to get the game working: > >> http://freelooser.fr/freebsd/patch-dlls__wined3d__swapchain_base.c > >> see bug: http://bugs.winehq.org/show_bug.cgi?id=23556 > > > >> now the problem related to amd64, when i start the game with windbg: > > If this is a problem related to amd64 (i.e. it does work under i386) then > > you could try to disable NX protection in your BIOS. > > > > I'm not sure of a way to only disable NX protection for wine under amd64. signature.asc Description: This is a digitally signed message part.
Re: sc2 with wine on amd64
On Sunday 11 July 2010 12:17:23 Mickaël Maillot wrote:
> Hi
>
> i try to play StarCraft 2 with wine on my amd64 8-STABLE desktop.
> first there is a patch to get the game working:
> http://freelooser.fr/freebsd/patch-dlls__wined3d__swapchain_base.c
> see bug: http://bugs.winehq.org/show_bug.cgi?id=23556
>
> now the problem related to amd64, when i start the game with windbg:
If this is a problem related to amd64 (i.e. it does work under i386) then you
could try to disable NX protection in your BIOS.
I'm not sure of a way to only disable NX protection for wine under amd64.
> WineDbg starting on pid 0019
> First chance exception: page fault on write access to 0x0037 in
> 32-bit code (0x7e66468f).
> Register dump:
> CS:0033 SS:003b DS:003b ES:003b FS:0013 GS:001b
> EIP:7e66468f ESP:0034f930 EBP:0034f9b8 EFLAGS:00010a02( R- --O I - - -
> ) EAX:0037 EBX:7e75f32c ECX:0003 EDX:0067
> ESI:0010 EDI:0010
> Stack dump:
> 0x0034f930: 031c 0010
> 0x0034f940: 0010 0010
> 0x0034f950: 0010 7ea66a1c 00133cd0
> 0x0034f960: 00cc0020 7e80dbc4 80808081
> 0x0034f970: 00010020 0037 0010
> 0x0034f980: 0010 0040 0021
> Backtrace:
> =>0 0x7e66468f create_alpha_bitmap+0x2af(color=0x318, mask=0x314,
> src_info=0x133cd0, color_bits=0x7ea66a1c)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:771]
> in user32 (0x0034fa38)
> 1 0x7e664ada create_icon_bitmaps+0x389(bmi=0x7ea669f4, width=0x0010,
> height=0x0010, color=0x34fa70, mask=0x34fa6c, alpha=0x34fa68)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:837]
> in user32 (0x0034fa98)
> 2 0x7e664ecb CURSORICON_CreateIconFromBMI+0x23a(bmi=0x7ea669f4,
> hotspot={x=0x0008, y=0x0008}, bIcon=0x0001, dwVersion=0x3,
> width=0x0010, height=0x0010, cFlag=0x8000)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:917]
> in user32 (0x0034faf8)
> 3 0x7e665914 CreateIconFromResourceEx+0x153(bits="(", cbSize=0x0468,
> bIcon=0x0001, dwVersion=0x3, width=0x0010, height=0x0010,
> cFlag=0x8000)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:1159
> ] in user32 (0x0034fb78)
> wineserver: file_set_error() can't map error: Bad address
> 4 0x7e665f42 CURSORICON_Load+0x311(hInstance=0x7e95, name=***
> invalid address 0x1 ***, width=0x0010, height=0x0010, depth=0x0020,
> fCursor=0, loadflags=0x8000)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:1292]
> in user32 (0x0034fbc8)
> wineserver: file_set_error() can't map error: Bad address
> 5 0x7e6693cb LoadImageW+0x1fa(hinst=0x7e95, name=*** invalid
> address 0x1 ***, type=0x0001, desiredx=0x0010, desiredy=0x0010,
> loadflags=0x8000)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:2392]
> in user32 (0x0034fc68)
> wineserver: file_set_error() can't map error: Bad address
> 6 0x7e668fed LoadImageA+0x4c(hinst=0x7e95, name=*** invalid
> address 0x1 ***, type=0x0001, desiredx=0x0010, desiredy=0x0010,
> loadflags=0x8000)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:2333]
> in user32 (0x0034fcc8)
> 7 0x7e97119e SIC_Initialize+0x1bd()
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/shell32/iconcache.c:417]
> in shell32 (0x0034fd08)
> 8 0x7e97e8c5 DllMain+0xe4(hinstDLL=0x7e95, fdwReason=0x0001,
> fImpLoad=0x1)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/shell32/shell32_main.c:1
> 166] in shell32 (0x0034fd38)
> 9 0x7e9c9e1a __wine_spec_dll_entry+0x69(inst=0x7e95,
> reason=0x0001, reserved=0x1)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/winecrt0/dll_entry.c:40]
> in shell32 (0x0034fd58)
> 10 0x7e44a925 call_dll_entry_point+0x14() in ntdll (0x0034fe58)
> 11 0x7e44ce77 MODULE_InitDLL+0x216(wm=0x1191e0, reason=0x0001,
> lpReserved=0x1)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/ntdll/loader.c:982]
> in ntdll (0x0034fec8)
> 12 0x7e44d211 process_attach+0x190(wm=0x1191e0, lpReserved=0x1)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/ntdll/loader.c:1071]
> in ntdll (0x0034ff38)
> 13 0x7e44d1c3 process_attach+0x142(wm=0x119130, lpReserved=0x1)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/ntdll/loader.c:1063]
> in ntdll (0x0034ffa8)
> 14 0x7e44d1c3 process_attach+0x142(wm=0x1186f8, lpReserved=0x1)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/ntdll/loader.c:1063]
> in ntdll (0x0034ffe8)
> 15 0x7e4515e4 attach_process_dlls+0x53(wm=0x1186f8)
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/ntdll/loader.c:2541]
> in ntdll (0x)
> 0x7e66468f create_alpha_bitmap+0x2af
> [/usr/ports/emulators/wine/work/wine-1.2-rc7/dlls/user32/cursoricon.c:771]
> in user32: movb %dl,0x0(%eax)
> Unable to open file ''
> Wine-dbg>
>
> the cursor does not have its bitmaps.
> the game crash few second laster with also a memory access problem.
signature.asc
Description
