DO NOT REPLY [Bug 5532] New: rsync / autoconf fails to detect libiconv on Solaris 10

samba-bugs at samba.org samba-bugs at samba.org
Tue Jun 10 03:02:15 GMT 2008


https://bugzilla.samba.org/show_bug.cgi?id=5532

           Summary: rsync / autoconf fails to detect libiconv on Solaris 10
           Product: rsync
           Version: 3.0.2
          Platform: Sparc
        OS/Version: Solaris
            Status: NEW
          Severity: minor
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: Greg.Robinson at dsto.defence.gov.au
         QAContact: rsync-qa at samba.org


Hi,

Solaris 10 Generic_127111-06 , gcc 3.4.3, built by sun in /usr/sfw/bin.

Problem:  autoconf fails to locate libiconv installed in /usr/local/lib, and
thus rsync fails to link.

I'd like to request that a note be put in the INSTALL documentation that
libiconv is a pre-requisite for rsync to build.  I couldn't find a mention of
it anywhere.

I suspect that configure should also bomb out with a fatal error if libiconv is
not detected.

Workaround:  setenv LDFLAGS -L/usr/local/lib  will detect and successfully
build and link an rsync binary.

Without the env var, configure gueses incorrectly:

checking for library containing libiconv_open... no
checking for iconv declaration... 
         extern size_t iconv (iconv_t cd, const char * *inbuf, size_t
*inbytesleft, char * *outbuf, size_t *outbytesleft);

With it set, it guesses correctly:

checking for library containing libiconv_open... -liconv
checking for iconv declaration... 
         extern size_t iconv (iconv_t cd, const char * *inbuf, size_t
*inbytesleft, char * *outbuf, size_t *outbytesleft);

I compile with these (working) options:

tcsh# setenv CC /usr/sfw/bin/gcc
tcsh# setenv LDFLAGS -L/usr/local/lib
tcsh# ./configure --with-rsyncd-conf=/usr/local/etc/rsyncd.conf
--datarootdir=/usr/local


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


More information about the rsync mailing list