From owner-freebsd-ports@FreeBSD.ORG Thu Feb 13 20:37:50 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79D1A1F0 for ; Thu, 13 Feb 2014 20:37:50 +0000 (UTC) Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [IPv6:2a01:e0c:1:1599::12]) by mx1.freebsd.org (Postfix) with ESMTP id 08758111A for ; Thu, 13 Feb 2014 20:37:48 +0000 (UTC) Received: from [192.168.1.18] (unknown [82.227.164.69]) by smtp3-g21.free.fr (Postfix) with ESMTP id 4C08BA61A3 for ; Thu, 13 Feb 2014 21:37:43 +0100 (CET) Message-ID: <52FD2D16.1000407@bebik.net> Date: Thu, 13 Feb 2014 21:37:42 +0100 From: Rodrigo OSORIO User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: configure fail in a test performed with -liconv X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 20:37:50 -0000 Hi all, I'm dealing with an issue in irc/scrollz port. The configure script fail and return a "getaddrinfo bug" caused by a failure when it compiles the conftest binary. In fact, conftest is compiled with the -liconv flag, but ld can't found it. Here is the command executed to compile the code cc -o conftest -O2 -pipe -fno-strict-aliasing -I/usr/local/include -I/usr/local/include -Wl,-rpath=/usr/lib:/usr/local/lib -Wl,-rpath=/usr/lib:/usr/local/lib conftest.c -lcrypt -L/usr/local/lib -L/usr/local/lib -liconv And the error /usr/bin/ld: cannot find -liconv cc: error: linker command failed with exit code 1 (use -v to see invocation) Iconv isn't required in any way by the application, but the flag is managed by the --enable-utf8 flag, if I call configure disabling utf8 support (--disable-utf8) config finish its work without error. Any idea or suggestion? Regards - rodrigo