From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RfZyd-0006wG-7B for garchives@archives.gentoo.org; Tue, 27 Dec 2011 16:34:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE1A021C093; Tue, 27 Dec 2011 16:33:56 +0000 (UTC) Received: from mx.virtyou.com (mx.virtyou.com [178.33.32.244]) by pigeon.gentoo.org (Postfix) with ESMTP id B2955E032F for ; Tue, 27 Dec 2011 16:32:48 +0000 (UTC) Received: from [192.168.2.43] (xdsl-78-35-163-245.netcologne.de [78.35.163.245]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx.virtyou.com (Postfix) with ESMTPSA id D6350DC02F for ; Tue, 27 Dec 2011 17:32:47 +0100 (CET) Message-ID: <4EF9F31B.3020103@wonkology.org> Date: Tue, 27 Dec 2011 17:32:27 +0100 From: Alex Schuster User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: [solved] Re: [gentoo-user] Build problems due to invalid libtool arguments References: <4EF8BB9F.1060200@wonkology.org> In-Reply-To: <4EF8BB9F.1060200@wonkology.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Archives-Salt: 5d59b3d7-d399-48af-a57f-154712979e49 X-Archives-Hash: 09f0f1194d63d9a0cbc626660a0d3b53 I wrote: > The problem is that in the libtool linking phase the arguments "/usr/bin > /usr/sbin /bin /sbin" are given along the libraries and library paths. I > have no idea why this happens, and how to solve this. Something must be > wrong on my system. But what? For libggi, emerging with USE=-aalib sort > of solved this. But I have no idea what to do about pygtksourceview. As > all gthe KDE stuff seems to depend on this, I cannot continue And the solution is : unset path I am using systemrescuecd, which sets a 'path' environment variable. This variable is being used in the libtool script, without being cleared first. Makes me feel a little stupid. I filed a bug report for a package that built without problems on my other system. I looked a bugs.gentoo.org, but did not search the web much for keywords like 'libtool' and '/usr/bin /usr/sbin /bin /sbin', which would have found a few mentions of this problem. And I wasted too much time debugging and trying to understand the libtool script. I filed a bug for autoconf: https://bugs.gentoo.org/show_bug.cgi?id=396213 Wonko