[nodisclaim]RE: FreeBSD Port: MailScanner-4.67.6_3

2008-11-13 Thread Koopmann, Jan-Peter
># mailscanner -debug >Fatal error 'Recurse on a private mutex.' at line 986 in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0) Not the slightest clue... perl with pthread enabled? I remember some problems with earlier versions... ___ free

FreeBSD Port: exim-4.69_1

2008-11-13 Thread Reinhard Haller
Hi, after updating exim-4.69 to 4.69_1 with portmanager -u -l I got the following new error messages: failed to open DB file /var/spool/exim/db/wait-remote_lmtp: Inappropriate file type or format IPv6 socket creation failed: Protocol not supported Exim runs in a jail, therefore there is no suppo

FreeBSD Port: MailScanner-4.67.6_3

2008-11-13 Thread Wim De Nocker (De Budelse)
Problem with Mailscanner setup on FreeBSD 6.2/6.3 After doing some updates on my ports collection (clamav, Sqlite, P5-IO-Net, and some others), mailscanner stopped working.. # mailscanner -debug Fatal error 'Recurse on a private mutex.' at line 986 in file /usr/src/lib/libpthread/thread/t

update from 6 to 7 - needs libtool rebuild

2008-11-13 Thread John Hein
I updated from 6-stable to 7-stable and got the following error when portupgrading graphics/tiff... . . /bin/sh /usr/local/bin/libtool --tag=CXX --mode=link c++ -O2 -fno-strict-aliasing -pipe -L/usr/local/lib -o libtiffxx.la -rpath /usr/local/lib -no-undefined -version-number 4:0:0 tif_s

Re: update from 6 to 7 - needs libtool rebuild

2008-11-13 Thread Jeremy Messenger
On Thu, 13 Nov 2008 11:06:04 -0600, John Hein <[EMAIL PROTECTED]> wrote: I updated from 6-stable to 7-stable and got the following error when portupgrading graphics/tiff... . . /bin/sh /usr/local/bin/libtool --tag=CXX --mode=link c++ -O2 -fno-strict-aliasing -pipe -L/usr/local/lib -o li

Re: update from 6 to 7 - needs libtool rebuild

2008-11-13 Thread Lowell Gilbert
John Hein <[EMAIL PROTECTED]> writes: > So my question is: is this documented and/or widely known? A full > portupgrade wouldn't help if you were up to date on libtool in 6.x > before updating (unless portupgrade -f is used). But you've *always* needed to rebuild *all* your ports when system lib

Re: update from 6 to 7 - needs libtool rebuild

2008-11-13 Thread John Hein
Lowell Gilbert wrote at 16:35 -0500 on Nov 13, 2008: > John Hein <[EMAIL PROTECTED]> writes: > > So my question is: is this documented and/or widely known? A full > > portupgrade wouldn't help if you were up to date on libtool in 6.x > > before updating (unless portupgrade -f is used). > >

Re: update from 6 to 7 - needs libtool rebuild

2008-11-13 Thread Lowell Gilbert
John Hein <[EMAIL PROTECTED]> writes: > I often don't rebuild everything right away and live with the compat > libs for a while. > > That has worked fine in the past (probably had some hiccups that I've > long since forgotten about). But I understand why the official > position is to rebuild ever

Re: update from 6 to 7 - needs libtool rebuild

2008-11-13 Thread Jeremy Messenger
On Thu, 13 Nov 2008 15:55:31 -0600, John Hein <[EMAIL PROTECTED]> wrote: Lowell Gilbert wrote at 16:35 -0500 on Nov 13, 2008: > John Hein <[EMAIL PROTECTED]> writes: > > So my question is: is this documented and/or widely known? A full > > portupgrade wouldn't help if you were up to date on

Time enough, and more

2008-11-13 Thread Ade Lovett
A plea, since there currently appears to be a worldwide epidemic of broken timepieces. If you (that'd be the generic you) see a port "miraculously fail", with something like the following in the configure output: [...] checking for a BSD-compatible install... /usr/bin/install -c -o root -