Re: How to start wine?
On Saturday 24 August 2013 23:12:57 Thomas Mueller wrote: I built wine from ports on a USB-stick installation of FreeBSD 9.1-STABLE i386, but it won't start. I tried to start from hard-drive installation of (from uname -a) FreeBSD amelia2 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #17 r254196: Sun Aug 11 00:36:49 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64 I get Shared object libwine.so.1 not found, required by wine I was able to find libwine.so and libwine.so.1 in directory /usr/local/lib, or as it is mounted, /compat/i386/usr/local/lib I tried as nonroot user. Kernel config includes the line options COMPAT_FREEBSD32# Compatible with i386 binaries What is the trick? Should I try to boot the USB stick with FreeBSD 9.1-STABLE i386? I did not build Xorg on this USB stick. Should I have? What is the requirement of FreeBSD versions matching? Although I keep the source tree, ports tree and work directories on the hard drive, installing to this Kingston Data Traveler 16 GB USB 2.0 stick is very slow, slower than NetBSD and slower than FreeBSD on other USB sticks. I could try with a Kingston Data Traveler 16 GB or 32 GB USB 3.0 drive. Tom You can't do that See https://wiki.freebsd.org/i386-Wine For a workaround, see https://people.freebsd.org/~ivoras/wine/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to start wine?
from dgmm: You can't do that See https://wiki.freebsd.org/i386-Wine For a workaround, see https://people.freebsd.org/~ivoras/wine/ I saw https://wiki.freebsd.org/i386-Wine Other page seems outdated. Can't do what? I built i386 Wine from i386. But it won't run without X. I could build an i386 installation to install on Kingston Data Traveler 16 GB or 32 GB USB 3.0, or install to a partition on a USB 3.0 hard drive. That USB 3.0 hard drive is not bootable, so I would have to put a boot image (giant floppy?) where I could boot from GRUB and mount root on the USB 3.0 hard drive partition. Problem with USB stick installation is frequent updates. So if I want installation to be portable, I might install to USB 3.0 hard drive partition. I have installed NetBSD (5-STABLE, 6-STABLE and HEAD, both i386 and amd64) to USB 2.0 sticks, and modular Xorg from pkgsrc too. NetBSD source trees, pkgsrc tree and work directories are on SATA hard drive. NetBSD is rather unstable on my hardware. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: deluge-1.3.6,1
Hi, I saw that you are the maintainer of the deluge port. With the port comes a startupscript (deluged), which I was able to adapt and configure so that at startup of freebsd the dummy user deluge starts the deluged script. This will run the demon, but not the webinterface (deluge-web), which I therefore have to start as the user logged on. Is there a way to have the user deluge also start the webinterface forked at startup? for instance could I duplicate the the deluged script to say 'delugew' and behave the same as deluged with the exception that instead of the deluge-demon it starts 'deluge-web --fork'? Or could I just add a line 'deluge-web --fork' to the existing script? As you can probably tell, I am pretty new to BSD, so I beg your forgiveness if my question seems ridiculous or out of line. Thanks for answering Georg ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/lightning | 1.2 | 2.0.0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to start wine?
On Saturday, 24 August 2013 15:12:57 Thomas Mueller wrote: I built wine from ports on a USB-stick installation of FreeBSD 9.1-STABLE i386, but it won't start. I tried to start from hard-drive installation of (from uname -a) FreeBSD amelia2 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #17 r254196: Sun Aug 11 00:36:49 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64 I get Shared object libwine.so.1 not found, required by wine This is because ld is looking for libwine.so.1 using the 64-bit library path. I was able to find libwine.so and libwine.so.1 in directory /usr/local/lib, or as it is mounted, /compat/i386/usr/local/lib I can suggest either: a) Making sure ldd(32) reports it can find the libraries (set LD_LIBRARY_PATH and LD_32_LIBRARY_PATH). Using those two environment variables should fix your problem b) Use the binary packages provided from either ports (i386-wine) or wiki.FreeBSD.org/i386-Wine. These include all the compatibility shims required. I tried as nonroot user. Kernel config includes the line options COMPAT_FREEBSD32# Compatible with i386 binaries What is the trick? Should I try to boot the USB stick with FreeBSD 9.1-STABLE i386? I did not build Xorg on this USB stick. Should I have? Hmmm, the last I heard Xorg does not run from a chroot... Wine would have pulled in libXorg so you should be fine (make sure DISPLAY is set correctly, usually to ':0'). What is the requirement of FreeBSD versions matching? Matching is very importantant, especially at the major version. Make sure the kernel is at a higher (or equal) version to the 32-bit binaries. Although I keep the source tree, ports tree and work directories on the hard drive, installing to this Kingston Data Traveler 16 GB USB 2.0 stick is very slow, slower than NetBSD and slower than FreeBSD on other USB sticks. I could try with a Kingston Data Traveler 16 GB or 32 GB USB 3.0 drive. Tom signature.asc Description: This is a digitally signed message part.
Re: How to start wine?
What are LD_LIBRARY_PATH and LD_32_LIBRARY_PATH supposed to be? I see neither of these environment variables defined. I tried to add /compat/i386... binary directories to the path, but that was insufficient. I see /lib /libexec /usr/lib /usr/lib32 /usr/libdata /usr/libexec /usr/local/lib /usr/local/libdata /usr/local/libexec with the FreeBSD i386 installation not mounted. I have seen LD_LIBRARY_PATH before from building packages from source. I thought maybe wineboot would set up the environment, but it looks like I have to set up the environment beforehand. What is the difference between the various wine ports in $PORTSDIR/emulators? I used wine-devel, newer but less tested than wine. Upstream latest release is 1.6 as far as I can see. Building X for FreeBSD i386 before wine would be necessary for running from i386 boot even if not runnable from amd64. My i386 version was/is somewhat behind amd64 version. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Bitmessage
Is there any interest in getting Bitmessage in ports? I heard about it on a podcast and it seems pretty interesting. https://bitmessage.org/wiki/Main_Page https://github.com/Bitmessage They've got a few FreeBSD-related commits, so maybe it wouldn't be too hard to port. Anyone wanna try? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
r253839 (stop recursively copying DT_NEEDED entries) and devel/ncurses
http://svnweb.freebsd.org/base?view=revisionrevision=253839 has made
ld(1) stop copying DT_NEEDED entries from shared libraries, which brings
us in line with what most of the Linux world has been doing for a while
and is a Good Thing (TM) since we stop adding implicit dependencies to
our binaries.
I've noticed one possible regression with devel/ncurses, though: most of
the time, simply passing -lncurses or -lncursesw to the linker like most
ports do will not work, since one also needs to pass -ltinfo or -tinfow.
This happens because we build devel/ncurses with --with-termlib (which
causes libtinfo{w}.so to be generated).
I guess this was not detected in exp-runs because devel/ncurses is not
normally pulled by ports with USES=ncurses (if a port is being built in
a chroot, Uses/ncurses.mk will just check that base's ncurses is
installed and ${LOCALBASE}/lib/libcurses.so does not exist and move on).
This can be easily tested by passing USES=ncurses:port to any port that
has USES=ncurses (such as devel/tig, security/pinentry or shells/zsh)
or, like in my case, just happening to have devel/ncurses installed
because x11/rxvt-unicode needs it.
On the Linux distributions I checked (Arch Linux, openSUSE and Ubuntu),
either ncurses was not build with --with-termlib (so libncurses{w}.so
would provide all the required symbols) or they have some multiarch
setup in place so that /usr/lib/arch-linux-gnu/libncurses{w}.so is an
ld script that has something like
INPUT(libncurses{w}.so AS_NEEDED(libtinfo{w}.so))
that solves the problem.
Right now, I'm not sure the best way to fix this is to patch each port
manually or stop passing --with-termlib in devel/ncurses.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
