AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

[O. Hartmann]

On Fri, 06 Sep 2013 21:11:26 +0400
Boris Samorodov <bsam at passap.ru> wrote:

> 06.09.2013 20:44, O. Hartmann пишет:
> > On Fri, 06 Sep 2013 20:08:59 +0400
> > Boris Samorodov <bsam at passap.ru> wrote:
> > 
> >> 06.09.2013 19:44, O. Hartmann пишет:
> >>
> >>> Here we go. It is the config.log from one of the failing machines,
> >>> failing in print/cups-client.
> >>
> >> Please, show the output of following commands (at the host in
> >> question): # svn info /usr/ports/
> >> # svn svn st /usr/ports/print/cups*
> >>
> > svn info /usr/ports/
> > 
> > Path: /usr/ports
> > Working Copy Root Path: /usr/ports
> > URL: svn://svn.de.freebsd.org/ports/head
> > Relative URL: ^/head
> > Repository Root: svn://svn.de.freebsd.org/ports
> > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> > Revision: 326523
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: danfe
> > Last Changed Rev: 326523
> > Last Changed Date: 2013-09-06 18:22:29 +0200 (Fri, 06 Sep 2013)
> > 
> > 
> > svn st /usr/ports/print/cups*
> > ?       /usr/ports/print/cups-base/work
> > ?       /usr/ports/print/cups-client/work
> 
> That is really stange... Some more info:
> # svn st /usr/ports/Mk
> # make -C /usr/ports/print/cups-client -V ICONV_LIB -V CONFIGURE_ARGS
> 

After this morning's reboot and restart of the update marathon, even
print/cups builds fine for now!

I have no clue what went wrong. I guess most evidences and traces are
gone with the restart of the boxes in question (they had all (3) the
same symptoms).

Thanks for looking into this,

Oliver