From owner-freebsd-current@FreeBSD.ORG Tue Oct 21 22:14:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FFFB16A4B3; Tue, 21 Oct 2003 22:14:49 -0700 (PDT) Received: from ms-smtp-02-eri0.southeast.rr.com (ms-smtp-02-lbl.southeast.rr.com [24.25.9.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 308BE43FBD; Tue, 21 Oct 2003 22:14:48 -0700 (PDT) (envelope-from wegster@mindcore.net) Received: from mindcore.net (rdu163-100-105.nc.rr.com [24.163.100.105]) h9M5EjR8012473; Wed, 22 Oct 2003 01:14:45 -0400 (EDT) Message-ID: <3F961244.2070809@mindcore.net> Date: Wed, 22 Oct 2003 01:14:44 -0400 From: Scott W User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 05:14:49 -0000 Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv were recompiled. I saved the log output and noticed several oddities I was wondering if anyone can explain? 1..several settings come up as undefined during the Perl build, namely: $i_malloc $d_setegid $d_seteuid $i_iconv These don't look troubling by themselves dur to 'autoconf magic,' but the next one for libiconv is more bothersome: From libiconv 1.9.1_3 configure: checking if libtool supports shared libraries... yes *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** bug-libtool@gnu.org Any ideas? Also, is there a way to pass configure options to portupgrade, or should I run make clean && ./configure for each port in an 'upgrade chain' and then force portupgrade to not make clean prior to building/installing? Thanks, Scott