Re: troubles rebuilding extensions.ini
On Sat, Jan 22, 2011 at 06:43:23AM +0100, Polytropon wrote: On Fri, 21 Jan 2011 22:57:07 -0500, Chris Brennan xa...@xaerolimit.net wrote: make rmconfig will remove/reset the config to factory default, then make config to restart fresh. And make rmconfig-recursive will do so for any other port the current port depends on. A very handy solution if the trouble hides in a dependency of a dependency... :-) Just see man ports for a list of all targets. Ye Gods. The ports manpage is almost unreadable. Not to mention full of non-ASCII bytes. I'm beat. Throwing in the towel for now. --Everything works except my own web server. Thanks to the list ... and that's it for now. --g -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.97a release of Jottings: http://jottings.thought.org ___ 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: troubles rebuilding extensions.ini
On Sat, 22 Jan 2011 00:18:28 -0800, Gary Kline kl...@thought.org wrote: On Sat, Jan 22, 2011 at 06:43:23AM +0100, Polytropon wrote: Just see man ports for a list of all targets. Ye Gods. The ports manpage is almost unreadable. Not to mention full of non-ASCII bytes. Those should be the representation of text attributes, rendered according to the terminals's capabilities (e. g. reverse, bold, underline). They should not be displayed as-is. What $PAGER are you using? It should be more or less more or less. :-) Try man -Pless ports and display should be fine. To get a readable PDF output of the manpage, use % zcat `man -w ports` | groff -Tps -dpaper=a4 -P-pa4 -mandoc | ps2pdf - ports.pdf % xpdf ports.pdf Select different format than A4 if needed, and PDF viewer respectively. Even % zcat `man -w ports` | groff -Tps -dpaper=a4 -P-pa4 -mandoc | gv - does work, omitting the PDF and presistent result file steps. In my opinion, man ports gives a good overview about all the targets common to ports, as well as the environmental variables that control the work of make in relation to the ports collection. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: troubles rebuilding extensions.ini
Gary Kline kl...@thought.org writes: On Sat, Jan 22, 2011 at 06:43:23AM +0100, Polytropon wrote: On Fri, 21 Jan 2011 22:57:07 -0500, Chris Brennan xa...@xaerolimit.net wrote: make rmconfig will remove/reset the config to factory default, then make config to restart fresh. And make rmconfig-recursive will do so for any other port the current port depends on. A very handy solution if the trouble hides in a dependency of a dependency... :-) Just see man ports for a list of all targets. Ye Gods. The ports manpage is almost unreadable. Not to mention full of non-ASCII bytes. I'm beat. Throwing in the towel for now. --Everything works except my own web server. Thanks to the list ... and that's it for now. It should not have any non-ASCII characters, or at least not properly displayable ones. That probably means that you have the wrong locale set for whatever your display is. If you just want to see only ASCII, then try 'LANG=C man ports'. If that doesn't work then try setting LC_ALL=C instead of LANG=C. -- Carl Johnsonca...@peak.org ___ 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: troubles rebuilding extensions.ini
On 01/22/11 09:43, Gary Kline wrote: It might be as simple as rebuilding php5-extensions _with_ the right .so files listed in /usr/local/etc/php/extension.ini; I have my doubts, but this is a first guess. IS there a way to include the make config when you are rebuilding the port? I can edit the makefile but I 'd rather do it the other way. tia, gary You can always try make config on any port to reset any options. Most of the time with php extensions its merely a case of reordering them though. Every build and upgrade changes things (extensions are added or removed, etc) so the order is changed as ports are only appended to the ini file. Keep a copy somewhere safe once you have it right and patch it as necessary- at least your web server will keep running that way. ___ 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: troubles rebuilding extensions.ini
On Fri, Jan 21, 2011 at 6:49 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: You can always try make config on any port to reset any options. Most of the time with php extensions its merely a case of reordering them though. Every build and upgrade changes things (extensions are added or removed, etc) so the order is changed as ports are only appended to the ini file. Keep a copy somewhere safe once you have it right and patch it as necessary- at least your web server will keep running that way. make rmconfig will remove/reset the config to factory default, then make config to restart fresh. ___ 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: troubles rebuilding extensions.ini
On Fri, 21 Jan 2011 22:57:07 -0500, Chris Brennan xa...@xaerolimit.net wrote: make rmconfig will remove/reset the config to factory default, then make config to restart fresh. And make rmconfig-recursive will do so for any other port the current port depends on. A very handy solution if the trouble hides in a dependency of a dependency... :-) Just see man ports for a list of all targets. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
