07.09.2013 01:51, 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 > > nothin (NULL output) > >> # make -C /usr/ports/print/cups-client -V ICONV_LIB -V CONFIGURE_ARGS >> > make -C /usr/ports/print/cups-client -V ICONV_LIB -V CONFIGURE_ARGS > > --localstatedir=/var > --disable-slp > --disable-gssapi --with-cups-user=cups > --with-cups-group=cups --with-system-groups=wheel > --with-docdir=/usr/local/share/doc/cups > --with-icondir=/usr/local/share/icons > --with-menudir=/usr/local/share/applications > --with-domainsocket=/var/run/cups.sock --with-cachedir=/var/db/cups > --with-pam-module="unix" --enable-ssl > --with-printcap=/usr/local/etc/printcap --disable-gnutls > --enable-openssl --without-php --disable-dnssd --disable-pam > --disable-ldap --disable-dbus --disable-libusb LIBS="-lssp_nonshared" > --prefix=/usr/local ${_LATE_CONFIGURE_ARGS} Well, the output is perfect. > I see a lot of those obscure libtool errors not finding libiconv.la. > Where the hell does the tool take those ecos from the past? I guess I > have to reboot the box after X11 has been compiled Did not see those. Since so far it seems that such errors are not common, may be something at your environment causes this (may be at /etc/make.conf)? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To ServeReceived on Fri Sep 06 2013 - 20:10:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:41 UTC