Re: GDAL 1.10 build fails on FreeBSD

2013-09-04 Thread Frank Broniewski
Am 2013-09-03 16:54, schrieb Rainer Hurling: Am 03.09.2013 15:11, schrieb Frank Broniewski: Hi all, I tried updating Gdal to the latest version on my FreeBSD system (9.1-RELEASE-p6), but the build fails: snip c postgisrasterdataset.cpp -fPIC -DPIC -o ../o/.libs/postgisrasterdataset.o

Mapserver shp2img

2013-09-04 Thread Frank Broniewski
Hi all, I've a problem with my mapserver installation, the utility shp2img isn't working. I get the following error when invoking it: /usr/local/bin/shp2img: error: `/usr/local/bin/.libs/shp2img' does not exist This script is just a wrapper for shp2img. See the libtool documentation for more

FreeBSD ports you maintain which are out of date

2013-09-04 Thread portscout
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,

gettext build problem on a jail

2013-09-04 Thread Andrea Zulato
Hi, i've a problem building gettext-0.18.3 on a jail, host is 8.3-RELEASE-p9 amd64. xz is giving me this error: Making all in misc if test no != no; then am__dir=. am__subdir_includes=''; case start-po.elc in */*) am__dir=`echo 'start-po.elc' | sed 's,/[^/]*$,,'`; am__subdir_includes=-L

Re: FreeBSD Port: net-p2p/transmission

2013-09-04 Thread Matthieu Volat
On Tue, 03 Sep 2013 13:48:20 -0400 Mike Jakubik mike.jaku...@intertainservices.com wrote: On 08/31/13 09:05, Matthieu Volat wrote: On Sat, 31 Aug 2013 09:21:56 +0100 cr...@bayofrum.net wrote: I'm sorry that I was unable to runtime test transmission-qt. I'll try to get an instance

Re: FreeBSD Port: net-p2p/transmission

2013-09-04 Thread Mike Jakubik
On 09/04/13 12:24, Matthieu Volat wrote: Weird, it seems to happen somewhere between the qt and the libevent libraries. At this point, I'd consider to : 1. try to run transmission-qt after renaming ~/.config/transmission and ~/.cache/transmission 2. report the issue upstream Did not help,

FreeBSD Port: net/svnup

2013-09-04 Thread Mike Jakubik
Hello, I am unable to get svnup to work on -CURRENT. When I run it, it just sits there doing nothing, but taking 100% cpu. I have only commeneted out the east mirror in the config file. 10.0-CURRENT FreeBSD 10.0-CURRENT #1: Wed Sep 4 17:06:59 EDT 2013 [root@freebsd-current /usr/src]# svnup

The Original VI ?

2013-09-04 Thread Ronald F. Guilmette
I've just been fiddling with some unicode/utf-8 stuff, and managed to figure out how to get both xterm and more (aka less) to properly deal with utf-8 characters. It then occured to me that it might be nice if I could cut and paste utf-8 stuff into vi, which is the text editor that I happen to

Re: The Original VI ?

2013-09-04 Thread olli hauer
On 2013-09-04 23:56, Ronald F. Guilmette wrote: I've just been fiddling with some unicode/utf-8 stuff, and managed to figure out how to get both xterm and more (aka less) to properly deal with utf-8 characters. It then occured to me that it might be nice if I could cut and paste utf-8 stuff

Re: The Original VI ?

2013-09-04 Thread Chad Perrin
On Thu, Sep 05, 2013 at 12:38:08AM +0200, olli hauer wrote: On 2013-09-04 23:56, Ronald F. Guilmette wrote: Apparently, it is correct that FreeBSD distributes nvi as vi (and as far as I can tell, that _does not_ currently support utf-8), but I sort-of thought that maybe this original vi,

Re: The Original VI ?

2013-09-04 Thread Zhihao Yuan
On Sep 4, 2013 3:55 PM, Chad Perrin c...@apotheon.net wrote: Is there some specific reason the nvi in base is stalled so far behind nvi-devel in terms of usability (by the way)? The nvi in CURRENT already supports UTF-8; if you want varies encodings, you need WITH_ICONV=1.

I got poudriere PHP port build errors, but the error isn't in my port

2013-09-04 Thread Darren Pilgrim
My port: mail/squirrelmail-postfixadmin-plugin Over the last two days I have received five Build failed messages from pkg-fallout, one each for {83,91}{amd64,i386} and head. The messages are quite long, but the juicy bits are below. The [...] indicates a gap in the log.