Re: FreeBSD Port: linuxpluginwrapper-20051113_8
On 2008-Sep-12 22:00:49 -0300, "Carlos A. M. dos Santos" <[EMAIL PROTECTED]> wrote: >I think www/nspluginwrapper is the best choice these days, since >linuxpluginwrapper seems to be an abandoned project. Unfortunately, nspluginwrapper is not a general replacement for linuxpluginwrapper - it is missing most of linuxpluginwrapper's functionality. nork@ also appears to be MIA - he hasn't responded to any of the other threads on linuxpluginwrapper being broken. For my specific requirements (running pips), I managed to hack a work-around but I don't believe it's committable. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgplMNsLiHRXH.pgp Description: PGP signature
Re: FreeBSD Port: linuxpluginwrapper-20051113_8
On Fri, 2008-09-12 at 22:00 -0300, Carlos A. M. dos Santos wrote: > I think www/nspluginwrapper is the best choice these days, since > linuxpluginwrapper seems to be an abandoned project. > I agree, and have been using nspw for quite some time. Still, if lpw remains in the ports tree, it ought to play nicely with the various port upgrading tools. Frank ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: linuxpluginwrapper-20051113_8
On Fri, Sep 12, 2008 at 9:12 PM, Frank Jahnke <[EMAIL PROTECTED]> wrote: > I updated my ports tree today, and a portsdb failed owing to > linuxpluginwrapper. This seems to be because acroread7 is no longer in > the ports tree, so the update fails. acroread7 is indeed in the > makefile. You may wish to update the port for lpw. > > Thanks for you attention! > > Frank Jahnke I think www/nspluginwrapper is the best choice these days, since linuxpluginwrapper seems to be an abandoned project. -- cd /usr/ports/sysutils/life make clean ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: linuxpluginwrapper-20051113_8
I updated my ports tree today, and a portsdb failed owing to linuxpluginwrapper. This seems to be because acroread7 is no longer in the ports tree, so the update fails. acroread7 is indeed in the makefile. You may wish to update the port for lpw. Thanks for you attention! Frank Jahnke ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
a $PREFIX question...
Greetings,
I'm attempting to create (hack) the current php5 port to permit
the installation of the CGI sapi along side php4 (CLI, and MOD sapi).
I /know/ where /want/ everything to go (believing I can make it work).
BUT, I'm not confident I have a firm grasp on the ports variables.
This is what I've done so far:
o edited the pkg-plist; modifying all references to php/ to php5/
eg;
bin/php5/
etc/php5/
include/php5/
lib/php5/
o edited (hacked) the following lines in the Makefile;
CONFIGURE_ARGS=
--with-config-file-scan-dir=${PREFIX}/etc/php5
...
post-install:
@${INSTALL_DATA} ${WRKSRC}/php.ini-dist ${PREFIX}/etc/php5
@${INSTALL_DATA} ${WRKSRC}/php.ini-recommended ${PREFIX}/etc/php5
@${INSTALL_DATA} ${WRKDIR}/php.conf ${PREFIX}/etc/php5
@${TOUCH} ${PREFIX}/include/php5/ext/php_config.h
NOW, here's where I fail to completely understand the $PREFIX &|
$LOCALBASE variables. I understand that $PREFIX if left undefined
defaults to $LOCALBASE (/usr/local). BUT, what must I define to
coerce the php5 CGI sapi (and depends) to simply use the php5 directory
as opposed to the default *php* directory?
Any help here would be GREATLY appreciated, as I hope to ultimately
turn this into a port. :)
Thank you for your time and consideration.
--Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SoundServer crashes
On September 10, 2008, L Campbell wrote: > artsd looks to be from the audio/arts; rebuilding it with > WITH_DEBUG=yes should enable debugging and disable stripping. Sorry, tried that, but neither the crash dump has a back-trace nor the gdnc-core can be analyzed. Both are as before. It looks like artsd is calling another program, which is causing the crash instead. What is the gdnc program that is crashing? > > On Wed, Sep 10, 2008 at 3:55 PM, Paul Horechuk <[EMAIL PROTECTED]> wrote: > > On September 10, 2008, आशीष शुक्ल Ashish Shukla wrote: > >> In <[EMAIL PROTECTED]>, Paul Horechuk wrote: > >> > >> [snip] > >> > >> >gdb gdnc.core > >> >GNU gdb 6.1.1 [FreeBSD] > >> >Copyright 2004 Free Software Foundation, Inc. > >> >GDB is free software, covered by the GNU General Public License, and > >> > you are welcome to change it and/or distribute copies of it under > >> > certain conditions. > >> >Type "show copying" to see the conditions. > >> >There is absolutely no warranty for GDB. Type "show warranty" for > >> > details. This GDB was configured as > >> > "i386-marcel-freebsd"..."/gdnc.core": not in executable format: File > >> > format not recognized > >> > >> I don't think above is the way to inspect core-dumps with gdb. > >> > >> % gdb > >> (gdb) core-file gdnc.core > >> > >> HTH > >> Ashish > > > > better, but, > > back produces... > > #0 0x2890b957 in ?? () > > #1 0x28829097 in ?? () > > #2 0x0287 in ?? () > > #3 0x0006 in ?? () > > #4 0xbfbfd654 in ?? () > > #5 0x in ?? () > > #6 0x2891f858 in ?? () > > #7 0xbfbfd68c in ?? () > > #8 0xbfbfd6a8 in ?? () > > #9 0x2890a499 in ?? () > > #10 0x0006 in ?? () > > #11 0xbfbfd68c in ?? () > > #12 0x in ?? () > > #13 0x0804eff0 in ?? () > > #14 0x in ?? () > > #15 0xbfbfd6d8 in ?? () > > #16 0x2804f469 in ?? () > > #17 0xffdf in ?? () > > #18 0x in ?? () > > #19 0x in ?? () > > #20 0x in ?? () > > #21 0x0804f674 in ?? () > > #22 0x0804eff0 in ?? () > > #23 0x in ?? () > > #24 0xbfbfd6d8 in ?? () > > #25 0x0804ce11 in ?? () > > #26 0x0817a5b8 in ?? () > > > > I think I need to put debugging in to get symbols. > > Which program do I recompile and what are the make options. > > > > Thanks for the clue for the core dump. > > > > -- > > Paul Horechuk > > Think Free > > Use Open Source Software > > > > __ > > This email has been scanned by the MessageLabs Email Security System. > > For more information please visit http://www.messagelabs.com/email > > __ > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" -- Paul Horechuk Think Free Use Open Source Software __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Balance - Port
On Fri, Sep 12, 2008 at 04:00:06PM +0300, Okalany Daniel wrote:
> Im on freebsd current with ports current.
> FreeBSD down.one2net.co.ug 8.0-CURRENT FreeBSD 8.0-CURRENT #7: Wed Sep 10
> 19:31:10 EAT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IPFWKERNEL
> i386
>
> [EMAIL PROTECTED] /usr/home/oka]# /usr/local/etc/rc.d/balance start
> setsockopt(IPV6_V6ONLY=0): Invalid argument
>
> Is this a problem with balancer or my options?
It appears you've removed IPv6 support from your kernel, which is fine.
The bug in with the IPv6 detection method used by balancer. The logic
in balancer is "if IPV6_V6ONLY is defined, call setsockopt() with
IPV6_V6ONLY". The definition is pulled in from one of many #include
files in /usr/include.
balancer assumes that if IPV6_V6ONLY is defined, that it should make
the setsockopt() call. This won't work for systems with IPv6 removed
from the kernel -- because the system #include files still define
IPV6_V6ONLY as an available bit.
Can you apply the following hackfix against ports/net/balancer/Makefile
and tell me if it works for you? Please note you'll need to build the
port either with "make WITHOUT_IPV6=true" or place WITHOUT_IPV6=true
in /etc/make.conf.
--- Makefile.orig 2008-07-09 00:15:46.0 -0700
+++ Makefile2008-09-12 07:00:44.0 -0700
@@ -20,6 +20,10 @@
MAN1= balance.1
+.if defined(WITHOUT_IPV6)
+CFLAGS+= -UIPV6_V6ONLY
+.endif
+
pre-build:
@${REINPLACE_CMD} -e 's|^CFLAGS|CFLAGS?|' \
-e 's|^CC|CC?|' ${WRKSRC}/Makefile
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mod_python core dump
On Fri, Sep 12, 2008 at 11:39:35AM +0200, Matias Surdi wrote: > I've installed mod_python from the ports on a recently installed FreeBSD > 7 box and, despite all the build process goes well, when I try to start > apache I get a core dump. If I disable the "Loadmodule" directive for > mod_python in httpd.conf, then apache starts perfectly. > > The versions I'm using are: > > # pkg_version -v > apache-2.0.63_2 = up-to-date with port > autoconf-2.62 = up-to-date with port > autoconf-wrapper-20071109 = up-to-date with port > bash-3.2.39_1 = up-to-date with port > dovecot-1.1.3 = up-to-date with port > expat-2.0.1 = up-to-date with port > gettext-0.17_1 = up-to-date with port > gmake-3.81_3= up-to-date with port > help2man-1.36.4_2 = up-to-date with port > libiconv-1.11_1 = up-to-date with port > libtool-1.5.26 = up-to-date with port > linux_base-fc-4_10 < needs updating (port has 4_13) > m4-1.4.11,1 = up-to-date with port > mod_python-3.3.1_2 = up-to-date with port > p5-gettext-1.05_2 = up-to-date with port > pcre-7.7_1 = up-to-date with port > perl-5.8.8_1= up-to-date with port > pkg-config-0.23_1 = up-to-date with port > postfix-2.5.4,1 = up-to-date with port > py25-sqlite3-2.5.2_1= up-to-date with port > python25-2.5.2_3= up-to-date with port > sqlite3-3.5.6 = up-to-date with port > > Any help will be appreciated, thanks. You'll need to provide a gdb backtrace to determine the cause of the core, and provide any error messages shown in Apache's error log (default: /var/log/httpd-error.log). The above information doesn't provide enough detail. Please also be aware that, quite often, debugging Apache and Apache modules is a tedious and difficult task. It's rarely a simple thing. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mod_python core dump
Hi, I've installed mod_python from the ports on a recently installed FreeBSD 7 box and, despite all the build process goes well, when I try to start apache I get a core dump. If I disable the "Loadmodule" directive for mod_python in httpd.conf, then apache starts perfectly. The versions I'm using are: # pkg_version -v apache-2.0.63_2 = up-to-date with port autoconf-2.62 = up-to-date with port autoconf-wrapper-20071109 = up-to-date with port bash-3.2.39_1 = up-to-date with port dovecot-1.1.3 = up-to-date with port expat-2.0.1 = up-to-date with port gettext-0.17_1 = up-to-date with port gmake-3.81_3= up-to-date with port help2man-1.36.4_2 = up-to-date with port libiconv-1.11_1 = up-to-date with port libtool-1.5.26 = up-to-date with port linux_base-fc-4_10 < needs updating (port has 4_13) m4-1.4.11,1 = up-to-date with port mod_python-3.3.1_2 = up-to-date with port p5-gettext-1.05_2 = up-to-date with port pcre-7.7_1 = up-to-date with port perl-5.8.8_1= up-to-date with port pkg-config-0.23_1 = up-to-date with port postfix-2.5.4,1 = up-to-date with port py25-sqlite3-2.5.2_1= up-to-date with port python25-2.5.2_3= up-to-date with port sqlite3-3.5.6 = up-to-date with port Any help will be appreciated, thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
