Re: texi2html problem
Doug Barton wrote: > Building texi2html without NLS results in this: > texi2html > Undefined subroutine &Locale::Messages::dgettext called at > /usr/local/bin/texi2html line 29628. Indeed, I can confirm that the application is currently unusable when compiled without NLS support. Will report this upstream and remove the without-nls option until I/they can come up with a fix. > msgexec: warning: Locale charset "UTF-8" is different from > input file charset "ASCII". > Output of 'msgexec' might be incorrect. This should be harmless as UTF-8 is a superset of ASCII; but it is probably useful to enforce the ASCII character set during build. > It would also be useful if you could make real options out of what you > have in the file already. Not sure what you mean by this: the options seem real enough. Regards, Johan pgpXVZ47MVTTS.pgp Description: PGP signature
Re: texi2html problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/09/2012 00:34, Johan van Selst wrote: > Doug Barton wrote: >> Building texi2html without NLS results in this: texi2html >> Undefined subroutine &Locale::Messages::dgettext called at >> /usr/local/bin/texi2html line 29628. > > Indeed, I can confirm that the application is currently unusable > when compiled without NLS support. Will report this upstream and > remove the without-nls option until I/they can come up with a fix. > >> msgexec: warning: Locale charset "UTF-8" is different from input >> file charset "ASCII". Output of 'msgexec' might be incorrect. > > This should be harmless as UTF-8 is a superset of ASCII; but it is > probably useful to enforce the ASCII character set during build. Thanks for looking into this. >> It would also be useful if you could make real options out of >> what you have in the file already. > > Not sure what you mean by this: the options seem real enough. make config ===> No options to configure - -- If you're never wrong, you're not trying hard enough -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP+oqKAAoJEFzGhvEaGryE/cUIANk6WukCTPzPLWw6lEv/2s87 xr3Qc0y2wvQr1iwQx8FP4mc6slMQHVdLlryEGZnjrocrs1T1caLuYN+te7+/Zxc6 QK2c74Z5RPHKKkgKUSMFReAvLKm9CZrW8n8Uz8s63Vi87A3KIexV2j775MtNzPXc qgIVbi1RXp3TCfDCGH/lGAJynR+21l/upMv673ZILE6gYWJhYrewo3zanewwddMX FLMOEKRnrV2b8mNzWzGpH/qS9M04ONTlpT6Wu4oujD7lQU15kDwIkw3axVvAlymb uaW/XuVhOKiP5B4QPwDxfdKXL/C3KglLr/Mm6C+XIobHdkgHF5WQOBefqGAZaCM= =HTFU -END PGP SIGNATURE- ___ 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: cvs commit: ports/x11/slim Makefile pkg-plist ports/x11/slim/files pam.conf slim.sh.in
Doug, good day. Sun, Jul 08, 2012 at 02:48:54AM -0700, Doug Barton wrote: > /usr/bin/c++ -DNEEDS_BASENAME -DPACKAGE=\"slim\" -DVERSION=\"1.3.4\" > -DPKGDATADIR=\"/usr/local/share/slim\" -DSYSCONFDIR=\"/usr/local/etc\" > -DUSE_CONSOLEKIT -O2 -pipe -fno-strict-aliasing -O2 -pipe > -fno-strict-aliasing -I/home/slim/work/slim-1.3.4 -I/usr/local/include > -I/usr/local/include/dbus-1.0/include -I/usr/local/include/dbus-1.0 > -I/usr/local/include/ConsoleKit/ck-connector > -I/usr/local/include/freetype2 -o CMakeFiles/slim.dir/image.cpp.o -c > /home/slim/work/slim-1.3.4/image.cpp > /home/slim/work/slim-1.3.4/image.cpp: In member function 'int > Image::readPng(const char*, int*, int*, unsigned char**, unsigned char**)': > /home/home-f/slim/work/slim-1.3.4/image.cpp:784: error: invalid use of > incomplete type 'struct png_struct_def' > /usr/local/include/png.h:872: error: forward declaration of 'struct > png_struct_def' This very error should be fixed by the patch files/patch-libpng-setjmp-image.cpp. Do you have that file? If yes, what version of PNG library do you have? And can I have a look at the file /home/slim/work/slim/1.3.4/image.cpp? -- Eygene Ryabinkin,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] pgpJ0ta4IpWc5.pgp Description: PGP signature
Re: texi2html problem
Doug Barton wrote: > >> It would also be useful if you could make real options out of > >> what you have in the file already. > > Not sure what you mean by this: the options seem real enough. > make config > ===> No options to configure The only relevant options are DOCS and NLS; they were never included in OPTIONS in the past (before I adopted this port). And indeed, many ports don't include DOCS and NLS in their OPTIONS today. My understanding is that most people who want to tweak these specific settings use a system-wide setting anyway. Is there some general policy on whether OPTIONS_DEFINE should be set for DOCS and NLS as well? Regards, Johan pgpRhst8OWbT8.pgp Description: PGP signature
Re: texi2html problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/09/2012 01:27, Johan van Selst wrote: > Doug Barton wrote: It would also be useful if you could make real options out of what you have in the file already. >>> Not sure what you mean by this: the options seem real enough. >> make config >> ===> No options to configure > > The only relevant options are DOCS and NLS; they were never included in > OPTIONS in the past (before I adopted this port). And indeed, many ports > don't include DOCS and NLS in their OPTIONS today. My understanding is > that most people who want to tweak these specific settings use a > system-wide setting anyway. I do have a knob in make.conf to disable NLS globally. Having OPTIONS for the port would allow me to easily enable it for this port. - -- If you're never wrong, you're not trying hard enough -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP+pamAAoJEFzGhvEaGryE/OgIAIZbSbLfkI4wfb47tIV4Q/MH p3XL1UFLOicV2hTpb6TtPSQKywoAMZqgqrF2FvT558aZowkbcH4tSmVwDDIYmP4q j6hr/ZpjB1CV1/0YA0fO3Q5MApmUCmaR1q8D3HYOeaF6dQ1utq1CUymfdRNoUelH ldRT3puJjsquk+GNHviId6j6tVcZqxWRXCLxkj7yB61X+MIa82KLskesiVwepcQa R1pBI44Br/3JbkYYD4I5M7qtMe/guAKn4ZU7DK5iupM24skaCzV8p0ikdZyca3SC 2Ro0+3ph54kuwM/CtSs9qGpw6tuOhKvs/qIhGaT14eXXB+TO4QX2+Be509OhzBo= =+A4m -END PGP SIGNATURE- ___ 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: texi2html problem
2012/7/9 Johan van Selst : > Doug Barton wrote: >> >> It would also be useful if you could make real options out of >> >> what you have in the file already. >> > Not sure what you mean by this: the options seem real enough. >> make config >> ===> No options to configure > > The only relevant options are DOCS and NLS; they were never included in > OPTIONS in the past (before I adopted this port). And indeed, many ports > don't include DOCS and NLS in their OPTIONS today. My understanding is > that most people who want to tweak these specific settings use a > system-wide setting anyway. > > Is there some general policy on whether OPTIONS_DEFINE should be set for > DOCS and NLS as well? > As far as I understand you have to include DOCS, NLS, and EXAMPLES in OPTIONS_DEFINE if your port uses them, but they are automatically set if not overridden. René ___ 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"
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/169728[maintainer update] textproc/ibus: update to 1.4.1 f ports/169722[patch] Update games/bzflag to 2.4.0 o ports/169721[New port] graphics/zathura-djvu - DJVU plugin to zath o ports/169719mount_smbfs refuses to connect over port 445 o ports/169717update for audio/freeswitch-sounds f ports/169716net-mgmt/ndpmon several problems with build and instal o ports/169662[MAINTAINER] Split THREADS patches to better support G f ports/169631audio/freeswitch-sounds - Port fail when enabling fren o ports/169628sysutils/devcpu-data f ports/169623Vendor update net-im/kmess-kde4 o ports/169615lang/f2c buggy port f ports/169613security/botan: Fix ECDSA for dns/powerdns and maybe o f ports/169612dns/powerdns: Fix botan/cryptopp dependency, make it o ports/169598winbind failure on ssh login, failed to mlock memory: f ports/169545graphics/libjpeg-turbo is a build conflict with java/o f ports/169521astro/weatherspect: Exiting with SIGUse of uninitializ o ports/169519[net/cvsup] socksify and cvsup cannot be used together o ports/169509New software "Netmagis" with FreeBSD ports o ports/169492databases/pecl-sqlite must be restored f ports/169430net-mgmt/flowviewer Makefile does not install scripts o ports/169383New Port: graphics/puf Photographer productivity tool f ports/169376Update port games/megaglest to 3.6.0.3 o ports/169371port graphics/sane-backends segfaults o ports/169366www/xpi-* ports need re-install after each Firefox upd f ports/169333[PATCH] sysutils/syslog-ng2: move sample config to EXA o ports/169332editors/xemacs-packages: wide-edit.el wrong mode o ports/169322New port: net/armsd: SMFv2/ARMS Service Adapter daemon o ports/169314graphics/ImageMagick fails to build: test failure o ports/169296New port: textproc/libcrm114 CRM114 C-callable Library o ports/169211new port: emulators/vboxtool, provides effective contr f ports/169165sysutils/fusefs-kmod: calling fchown(2) on sshfs files o ports/169095New port: audio/mous "A simpe yet powerful audio playe o ports/169090New Port: comms/ge-x2212-2 An EEPROM programmer for GE o ports/169074[NEW PORT] net/jicmp6: ICMPv6 JNI f ports/169043Add CONFLICTS_INSTALL=fusefs-ntfs to sysutils/ntfsprog f ports/169032Update net-im/qutim port to 0.3.0 f ports/168935www/firefox-remote shares PORTNAME with www/firefox o ports/168926Second '59.xxx' out of range 0..59 at security/snort-r o ports/168861devel/tkcvs: tkdiff no longer runs correctly f ports/168611conflict: cad/brlcad: Port shares files with other por o ports/168486[PATCH] www/sams, warnings "strftime() [function.strft o ports/168466[PATCH] www/sams, web-interface, needs GetHostnameSam. f ports/168407[patch] lang/gauche: update to 0.9.3.2, unbreak o ports/168404[NEW PORT] databases/dev-sqlite3: This is a developmen o ports/168385every port has vulnerabilities in case of locale probl o ports/168328[REPOCOPY] devel/codeblocks --> devel/codeblocks-devel f ports/168319graphics/qiviewer: Not displaying image jpeg s ports/168215[PATCH] print/scribus-devel: update to 1.5.0 svn s ports/168161[PATCH] sysutils/conky: update to 1.9.0 f ports/168160ports-mgmt/jailaudit doesn't return a non-0 exit code o ports/168141faild to install lang/ezm3 s ports/167955[update] graphics/tinyows: Fix dependency to postgis f ports/167950databases/memcachedb does not work on 10-CURRENT f ports/167691security/heimdal: problem compiling kerberos/heimdal o ports/167591security/openssh-portable looks for ecdsa key but none o ports/167554security/openssh-portable has some drawbacks o ports/167428net/samba36 could not be configured to start only nmbd f ports/167090sysutils/ezjail: Invalid command line option in ezjail o ports/167042New port: net-p2p/tahoe-lafs f ports/167031security/heimdal ignore environment after process call f ports/166987net/nss_ldap: ports/152982 causes nss_ldap to not func o ports
Re: texi2html problem
Johan van Selst wrote: > Doug Barton wrote: > > Building texi2html without NLS results in this: > > texi2html > > Undefined subroutine &Locale::Messages::dgettext called at > > /usr/local/bin/texi2html line 29628. > Indeed, I can confirm that the application is currently unusable when > compiled without NLS support. Will report this upstream and remove the > without-nls option until I/they can come up with a fix. I have included a fix that seems to do the trick. The port should now work when built without NLS support as well. Do let me know if it still causes trouble. I must admit that NLS support is included by default for all ports on my systems. Johan pgpp59L3hLKjJ.pgp Description: PGP signature
Wine-fbsd64 updated to 1.5.8 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.8 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.8,1.tbz) = bc57b6b573816d24837c9171e38cdfaf MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.8,1.txz) = 4c06fd3e68c43c977449ab9f824f69dd MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.8,1.txz) = 34cce0d89ef9d3db47f7699a3769a6cd [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 * pkgng support for nVidia patching should be working properly and using a mixed mode between pkgng and pkg also works signature.asc Description: This is a digitally signed message part.
Re: Shar file too large
On Fri, Jul 6, 2012 at 11:14 PM, Chris Rees wrote: > On 6 July 2012 20:31, Fernando Apesteguía > wrote: >> On Fri, Jul 6, 2012 at 9:16 PM, Chris Rees wrote: >>> On 6 July 2012 20:14, Fernando Apesteguía >>> wrote: Hi, I'm trying to send a shar(1) file for a new port but it exceeds the 100 KB limit (344 KB) mainly because of the size of the pkg-plist file. Is there an alternative way to upload the file? >>> >>> Do you have any web space available? >> >> Try this out: >> >> https://www.dropbox.com/s/ipcwfgztpvh7z81/visualparadigm.shar.txt >> >>> >>> If not email it to me and I'll put it up for you. > > Great, put that link in your PR. Done[1]. Sorry, I was AFK the whole weekend. [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=169741 > > Chris ___ 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"
Wesnoth Port
I would be willing to take over maintainership of the Wesnoth port as I see Philip just gave it up. I am already maintaining a few other ports. Thanks! Rusty Nejdl ___ 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: Wesnoth Port
On Mon, Jul 09, 2012 at 12:40:07PM -0500, Rusty Nejdl wrote: > I would be willing to take over maintainership of the Wesnoth port as I > see Philip just gave it up. I am already maintaining a few other ports. Ok. I will commit ports/169144 and update maintainer soon. -- Alex ___ 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"
Clarification about redports.org
Hi there, I just created an account at redports.org. While reading the user guide, I found the following paragraph: "Notice: All ports in your repository replace the complete directory of the official ports whenever you build a port." I don't know if I understood correctly. Does it _really_ mean the directory of the official ports? The one users update for instance executing "freebsd-update fetch udpate"? ___ 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: Clarification about redports.org
On 9 July 2012 19:19, Fernando Apesteguía wrote: > Hi there, > > I just created an account at redports.org. While reading the user > guide, I found the following paragraph: > > "Notice: All ports in your repository replace the complete directory > of the official ports whenever you build a port." > > I don't know if I understood correctly. Does it _really_ mean the > directory of the official ports? The one users update for instance > executing "freebsd-update fetch udpate"? No. What it means is that *when you test the tree* the ports tree is mounted, and then your changes are applied to it (like a unionfs). This means that if you've modified a port that the tested port depends on, that one will also be tested. For example: I use my redports account and commit some changes to net-p2p/transmission-cli I want to test my changes to the slaves too, so I queue some builds for net-p2p/transmission-daemon. These use the modified transmission-cli. Chris ___ 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"
Where ports enhancing discussion going?
Hello all. I'm new on this list, but I'm using ports for a some years. Where do discussion about enhancing ports system goes? For example, I have some idea, which can be read here https://github.com/pkgng/pkgng/issues/100 Who could mentor/approve/review such changes and proposals? Thanks. -- Regards, Alexander Yerenkow ___ 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"
www/libxul fails to upgrade if devel/libunwind is installed
If devel/libunwind is installed, a portupgrade of www/libxul fails with: nsStackWalk.cpp: In function 'nsresult NS_StackWalk(void (*)(void*, void*), PRUint32, void*)': nsStackWalk.cpp:1544: error: '_Unwind_Backtrace' was not declared in this scope gmake[4]: *** [nsStackWalk.o] Error 1 gmake[4]: *** Waiting for unfinished jobs gmake[4]: Leaving directory `/usr/ports/www/libxul/work/mozilla-1.9.2/xpcom/base' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/libxul/work/mozilla-1.9.2/xpcom' gmake[2]: *** [libs_tier_xpcom] Error 2 gmake[2]: Leaving directory `/usr/ports/www/libxul/work/mozilla-1.9.2' gmake[1]: *** [tier_xpcom] Error 2 gmake[1]: Leaving directory `/usr/ports/www/libxul/work/mozilla-1.9.2' gmake: *** [default] Error 2 *** Error code 1 Stop in /usr/ports/www/libxul. *** Error code 1 Stop in /usr/ports/www/libxul. Simply deinstall libunwind (it is required by blender), and libxul upgrades without problem. Has anyone else seen this? I first became aware of this through this thread[1] on the forums. References: 1) http://forums.freebsd.org/showthread.php?p=183072 -- Regards, Torfinn Ingolfsen ___ 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: Where ports enhancing discussion going?
On 9 July 2012 12:13, Alexander Yerenkow wrote: > Hello all. > I'm new on this list, but I'm using ports for a some years. > Where do discussion about enhancing ports system goes? > For example, I have some idea, which can be read here > https://github.com/pkgng/pkgng/issues/100 > Who could mentor/approve/review such changes and proposals? The discussion takes place on this list usually. When a patch is available it gets sent as a PR to GNATS http://www.freebsd.org/send-pr.html > Thanks. -- Eitan Adler ___ 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: Clarification about redports.org
On Mon, Jul 9, 2012 at 8:27 PM, Chris Rees wrote: > On 9 July 2012 19:19, Fernando Apesteguía > wrote: >> Hi there, >> >> I just created an account at redports.org. While reading the user >> guide, I found the following paragraph: >> >> "Notice: All ports in your repository replace the complete directory >> of the official ports whenever you build a port." >> >> I don't know if I understood correctly. Does it _really_ mean the >> directory of the official ports? The one users update for instance >> executing "freebsd-update fetch udpate"? > > No. What it means is that *when you test the tree* the ports tree is > mounted, and then your changes are applied to it (like a unionfs). > > This means that if you've modified a port that the tested port depends > on, that one will also be tested. > > For example: > > I use my redports account and commit some changes to net-p2p/transmission-cli > > I want to test my changes to the slaves too, so I queue some builds > for net-p2p/transmission-daemon. > > These use the modified transmission-cli. It's much clearer now. Thanks! > > Chris ___ 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: unbroken dev/icu in current
On 07/06/12 09:59, Ruslan Mahmatkhanov wrote: Hi Rodrigo, Rodrigo OSORIO wrote on 04.07.2012 00:33: On 07/03/12 21:20, Ruslan Mahmatkhanov wrote: Why to not just ask Rodrigo to update? I think this BROKEN is only needed if icu doesn't builds on a system, that was installed from official FreeBSD -current snapshot. If memory serves me well there is many extra cautions in docs that using -current, csuped in wrong time, may produce various problems, so "It's a -current, babe" should sound reasonable, I believe. Is there any extra info (error logs), or was you able to reproduce it on some of your -current system? Rodrigo, can you please update your system and check if problem is gone? Ruslan, I have a check of the fix planed for tomorrow. But I'll focus my tests in dependencies. Sorry I somehow missed your response. Was your icu problem solved with system update? If yes, please let Chris know about that, so he doesn't mark it BROKEN, because it looks like it was some temporary mess in repository. Hi, Good news, the latest current sources makes icu happy. I didn't test other icu things too much but the ports compiles and install without error. Afaik we can consider the port unbroken on current. Your sources tells the true Chris ! Regards - rodrigo ___ 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: Wesnoth Port
On 09 Jul 2012, at 19:40, Rusty Nejdl wrote: > I would be willing to take over maintainership of the Wesnoth port as I see > Philip just gave it up. I am already maintaining a few other ports. Thanks for volunteering. :) I knew a kind soul would quickly snap up maintainership. Apologies for sitting on this for so long. - Philip -- Philip Paeps Senior Reality Engineer Ministry of Information ___ 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: texi2html problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/09/2012 04:12, Johan van Selst wrote: > Johan van Selst wrote: >> Doug Barton wrote: >>> Building texi2html without NLS results in this: >>> texi2html >>> Undefined subroutine &Locale::Messages::dgettext called at >>> /usr/local/bin/texi2html line 29628. >> Indeed, I can confirm that the application is currently unusable when >> compiled without NLS support. Will report this upstream and remove the >> without-nls option until I/they can come up with a fix. > > I have included a fix that seems to do the trick. The port should now > work when built without NLS support as well. Do let me know if it still > causes trouble. I was able to build it no problem WITHOUT_NLS. It also gives the proper error message when run with no input, and produces the docs for ffmpeg without any problems. Thanks for your prompt attention to this. :) > I must admit that NLS support is included by default for > all ports on my systems. No problem at all. I realize I'm using a non-default configuration. Doug - -- If you're never wrong, you're not trying hard enough -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP+8wWAAoJEFzGhvEaGryExXcH/jNitFGu9x64uZUi/oirL0kL rVVP2s/tOypB0/4z+LwFYaDpdRIJ5DrRkah81odySe+KDe5LyKNCmDmd+PayfvK8 OWVnGAktfFa5AfMjYFXzxpHRl6/W3skUbesXts98BCzd501fbuY4d7eXSy+nWmkQ FpSk8aKA1kPl37sXEJvlV6/FYpGF4XAxVIJGjPFCLONcBrZFnPnoiDuzH5C/GtY7 WME/FDCmeJnbDEjuNCV51aZkg7ed3EmSSKtveBSREMfpSlgJFGCaD/TDmaz26a0M 6k9K0ynNB+KnWlH6PkrdpRjnPFVaR8h+ykegakuGCT77G2sCnMXRAs5GZ3YarzE= =/Zb5 -END PGP SIGNATURE- ___ 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"
