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 naylor.b.da...@gmail.com 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.
Re: Wrong version of sources?
On Sun, 02 Sep 2012 08:51:33 +0300, Alexander Kapshuk wrote: On 09/02/2012 03:21 AM, Walter Hurry wrote: My standard- supfile (copied from examples with only the default host changed) says 'tag=RELENG_9'. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html RELENG_9 The line of development for FreeBSD-9.X, also known as FreeBSD 9-STABLE You're running 9.1-RC1, which doesn't have the RELENG_9_1 tag available yet, as this is a release candidate. Thus the trouble when compiling VBox from sources. Have you rebuilt your kernel and the world once you'd pulled in the sources for RELENG_9? Anyway, that's my take on it. Thanks for the reply. No, I haven't rebuilt kernel and world, nor do I intend to for the moment. I'm happy to stick with generic. I'm still slightly confused by this tag stuff though; sorry (despite perusal of the handbook). Are you saying that until RELENG_9_1 is made available I won't be able to compile kernel modules? Or that I should have a different tag in my standard-supfile? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Wrong version of sources?
[ Walter Hurry wrote on Sun 2.Sep'12 at 13:19:44 + ] On Sun, 02 Sep 2012 08:51:33 +0300, Alexander Kapshuk wrote: On 09/02/2012 03:21 AM, Walter Hurry wrote: My standard- supfile (copied from examples with only the default host changed) says 'tag=RELENG_9'. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html RELENG_9 The line of development for FreeBSD-9.X, also known as FreeBSD 9-STABLE You're running 9.1-RC1, which doesn't have the RELENG_9_1 tag available yet, as this is a release candidate. Thus the trouble when compiling VBox from sources. Have you rebuilt your kernel and the world once you'd pulled in the sources for RELENG_9? Anyway, that's my take on it. Thanks for the reply. No, I haven't rebuilt kernel and world, nor do I intend to for the moment. I'm happy to stick with generic. I'm still slightly confused by this tag stuff though; sorry (despite perusal of the handbook). Are you saying that until RELENG_9_1 is made available I won't be able to compile kernel modules? Or that I should have a different tag in my standard-supfile? To have the 9.1-RC1 source code, use the stable-supfile in /usr/share/examples/cvsup/ and build world and kernel using that source tree. That will give you a 9.1-RC1 system. So that would be a RELENG_9 tag if you look in that stable-supfile. Then, when 9.1-RELEASE is officially released, you'd use the standard-supfile which uses a RELENG_9_1 tag if you wanted to stay with the -RELEASE brach. Or you could just continue to track stable branch and keep the RELENG_9 tag. That's what I am doing currently although I intend on tracking stable branch anyway, i.e. after 9.1-RELEASE has been made available. Jamie. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Wrong version of sources?
On 09/02/12 16:19, Walter Hurry wrote: Thanks for the reply. No, I haven't rebuilt kernel and world, nor do I intend to for the moment. I'm happy to stick with generic. By using the RELENG_9 tag, you're tracking the STABLE development branch. By pulling in the sources for the STABLE development branch and rebuilding the kernel and the world by following the instructions given in the Handbook, you are sticking with the GENERIC kernel configuration, unless you build a custom kernel. I'm still slightly confused by this tag stuff though; sorry (despite perusal of the handbook). Are you saying that until RELENG_9_1 is made available I won't be able to compile kernel modules? Or that I should have a different tag in my standard-supfile? That's right. RELENG_9_1 isn't available yet. The options available to you now, as far as I can tell, are: (1). Do not recompile the kernel and the world, if you want to track 9.1-RC, to be followed by RELENG_9_1, once it becomes available. You may use freebsd-update(8), to keep the system up-to-date by way of binary updates. Once release 9.1 is out, you may change RELENG_9 in your sup-file to RELENG_9_1, and then you'll be tracking the release branch and you'll be able to keep the kernel and the world up-to-date by way of source updates. Use pkg_add(1) to install VBox. (2). Stick with RELENG_9, which is the STABLE development branch. Pull in the latest sources. Rebuild the kernel and the world. You may be prompted to rebuild the ports installed on your system as well. Use pkg_add(1) or the ports to install software. If any one else on the list thinks otherwise, as they are more experienced folk on the list than I, I'd be happy to stand corrected. Hope the above helps. Alexander Kapshuk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Wrong version of sources?
On 02/09/2012 14:33, Jamie Paul Griffin wrote: To have the 9.1-RC1 source code, use the stable-supfile in /usr/share/examples/cvsup/ and build world and kernel using that source tree. That will give you a 9.1-RC1 system. So that would be a RELENG_9 tag if you look in that stable-supfile. Then, when 9.1-RELEASE is officially released, you'd use the standard-supfile which uses a RELENG_9_1 tag if you wanted to stay with the -RELEASE brach. Or you could just continue to track stable branch and keep the RELENG_9 tag. While this advice was correct for all previous FreeBSD releases, cvsup(8) support for 9.1-RELEASE is not going to be provided. See this message from re@: http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/069233.html Ken Smith wrote: With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. Instead, you will be able to use freebsd-update to track 9.1-RELEASE (including system sources), or you can use SVN to follow the releng/9.1 branch. You will still be able to use cvsup to track RELENG_9 aka. 9.1-STABLE aka. stable/9. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
to move csup 90 to subversion 91rc
Hello,
If my csup file looks about like this:
*default host=this_working_mirror
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_9_0
*default delete use-rel-suffix
and my machine now has devel/subversion
what is the quickest way to get the new release candidate sources with
svn?
Then, can I simply build{w,k}, install{w,k} as before?
Regards,
Darrel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Sharing COM ports to Windows hosts
Colleagues, There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? Actually, does anyone have a success story for such a scenario? There is some software like comms/serialoverip, comms/tits etc but are there any (freeware) Windows virtual COM port drivers compatible therewith? Maybe some Windows drivers for hardware console servers (like Moxa) would work with tits etc? Thanks a lot for any advice. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
