Re: KSE howto?
On 9 Sep 2003 at 17:06, Jesse Guardiani wrote: Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... I just enable libkse on 5.1-RELEASE. Do this: 1 - add WITH_LIBMAP= yes to /etc/make.conf 2 - do a make clean in src/libexec/rtld-elf and make all install 3 - to /etc/libmap.conf, add: libc_r.so.5 libkse.so.1 libc_r.so libkse.so I cvsup'ed with current Sept. 25'th and noticed changes to libpthread. So I did a 'make world/kernel' and Firebird (browser) and Thunderbird (mail) haven't crashed since then. Before the 'make world/kernel' these two apps would crash at regular intervals, and I had to make these addititions to /etc/libmap.conf so they wouldn't go down: [/usr/X11R6/bin/firebird] libc_r.so.5 libthr.so.1 libc_r.solibthr.so regards Claus Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)
Claus Guttesen wrote: Before the 'make world/kernel' these two apps would crash at regular intervals, and I had to make these addititions to /etc/libmap.conf so they wouldn't go down: [/usr/X11R6/bin/firebird] libc_r.so.5 libthr.so.1 libc_r.solibthr.so Which begs the question... is 5.2 going to ship with WITH_LIBMAP enabled by default? -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)
On Friday, Sep 26, 2003, at 13:29 US/Eastern, Terry Lambert wrote: Which begs the question... is 5.2 going to ship with WITH_LIBMAP enabled by default? http://www.google.com/search?q=libmap+default+WITH_LIBMAPie=UTF- 8oe=UTF-8 http://people.freebsd.org/~bmah/relnotes/CURRENT/relnotes-i386.txt rtld(1) now includes ``libmap'' functionality by default; the WITH_LIBMAP compile knob is unnecessary and has been retired. More information can be found in libmap.conf(5). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)
On Fri, 26 Sep 2003, Terry Lambert wrote: Claus Guttesen wrote: Before the 'make world/kernel' these two apps would crash at regular intervals, and I had to make these addititions to /etc/libmap.conf so they wouldn't go down: [/usr/X11R6/bin/firebird] libc_r.so.5 libthr.so.1 libc_r.solibthr.so Which begs the question... is 5.2 going to ship with WITH_LIBMAP enabled by default? It's already enabled by default, so I'd think so: revision 1.25 date: 2003/09/13 21:50:35; author: mdodd; state: Exp; lines: +1 -10 Retire the WITH_LIBMAP compile knob; libmap is now a standard feature. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Will 5.2 ship with WITH_LIBMAP? (was Re: KSE howto?)
Jeroen C.van Gelderen wrote: On Friday, Sep 26, 2003, at 13:29 US/Eastern, Terry Lambert wrote: Which begs the question... is 5.2 going to ship with WITH_LIBMAP enabled by default? http://www.google.com/search?q=libmap+default+WITH_LIBMAPie=UTF- 8oe=UTF-8 http://people.freebsd.org/~bmah/relnotes/CURRENT/relnotes-i386.txt rtld(1) now includes ``libmap'' functionality by default; the WITH_LIBMAP compile knob is unnecessary and has been retired. More information can be found in libmap.conf(5). I saw that in the release notes; but people are still posting to -current about problems that require it, and other are posting about how to use it, so either their -current isn't, or the code doesn't match the release notes. I suspect the former, but I wanted to make sure (5.2 is going to be my next big upgrade the old boxes release). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
KSE howto?
Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KSE howto?
On Tue, 9 Sep 2003, Jesse Guardiani wrote: Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... It will be easier to wait for ports@ to work out the issue with -pthread being removed. Then you should be able to set PTHREAD_LIBS=-lkse in /etc/make.conf and rebuild your ports. Until then, libmap.conf(5) is the easiest solution. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KSE howto?
On 9 Sep 2003 at 17:06, Jesse Guardiani wrote: Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... WOW! A -current question I can answer. I just enable libkse on 5.1-RELEASE. Do this: to use libkse under 5.*, 1 - add WITH_LIBMAP= yes to /etc/make.conf 2 - do a make clean in src/libexec/rtld-elf and make all install 3 - to /etc/libmap.conf, add: libc_r.so.5 libkse.so.1 libc_r.so libkse.so run. See also http://www.FreeBSD.org/cgi/man.cgi?query=libmap.confsektion=5apropos =0manpath=FreeBSD+5.1-RELEASE -- Dan Langille : http://www.langille.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KSE howto?
On 9 Sep 2003 at 17:09, Daniel Eischen wrote: On Tue, 9 Sep 2003, Jesse Guardiani wrote: Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... It will be easier to wait for ports@ to work out the issue with -pthread being removed. Then you should be able to set PTHREAD_LIBS=-lkse in /etc/make.conf and rebuild your ports. Until then, libmap.conf(5) is the easiest solution. Oh, well, perhaps my answer isn't correct after all... :( -- Dan Langille : http://www.langille.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KSE howto?
On Tue, 9 Sep 2003, Dan Langille wrote: On 9 Sep 2003 at 17:09, Daniel Eischen wrote: On Tue, 9 Sep 2003, Jesse Guardiani wrote: Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... It will be easier to wait for ports@ to work out the issue with -pthread being removed. Then you should be able to set PTHREAD_LIBS=-lkse in /etc/make.conf and rebuild your ports. Until then, libmap.conf(5) is the easiest solution. Oh, well, perhaps my answer isn't correct after all... :( Sure it is skipper. It's correct for the second part of my answer. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
