print/cups: 10.0-CURRENT renders cups unusable / recompilation fails due to missing libiconv

O. Hartmann ohartman at zedat.fu-berlin.de
Mon Aug 26 13:54:20 UTC 2013


Today I update a box to 10.0-CURRENT #0 r254896: Mon Aug 26 09:42:48
CEST 2013 amd64. Bevor the update this morning, I ran a box with the
sources from around last Friday and port print/cups was working fine
so far.

After building/installation of world/kernel today as of r254896 the
cups daemon didn't respond when accessd locally via port 631, printing
is rejected with messages like "reset by peer" and furthermore, when I
thought the cups binary might be out of sync with the environment, I
tried to recompile the whole preint/cups installation, but this fails
now in a close to EPICAL way not finding "libiconv" 

[...]
 cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler
-L/usr/local/lib -Wl,-rpath=/usr/lib:/usr/local/lib
-Wl,-R/usr/local/lib   -Wall -Wno-format-y2k -Wunused -fPIC -Os -g
-fstack-protector -Wno-tautological-compare -o bannertops bannertops.o
pstext.o common.o -lcupsimage \ -lcups  -lssl -lcrypto  -lz -pthread
-lcrypt -lm -lssp_nonshared ../cups/libcups.so: undefined reference to
`libiconv' ../cups/libcups.so: undefined reference to
`libiconv_close' ../cups/libcups.so: undefined reference to
`libiconv_open'

Well, freeBSD 10.0-CUR seems now "out of cups" as far as I can see. The
old installation is not working since it now rejects connections, a
recompilation isn't possible due to the libiconv issue.

What happens here, how can this problem be solved?

Regards,

Oliver

P.S. Sorry for cross posting, but I think this is for both CURRENT and
PORT list of interest.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20130826/ff7d60c7/attachment.sig>


More information about the freebsd-current mailing list