From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5218F1382C5 for ; Wed, 27 May 2020 14:44:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BA784E08F2; Wed, 27 May 2020 14:44:24 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 63282E08C2 for ; Wed, 27 May 2020 14:44:24 +0000 (UTC) Subject: Re: [gentoo-user] matplotlib build fails: link using /usr/lib instead of /usr/lib64 To: gentoo-user@lists.gentoo.org References: From: Michael Orlitzky Message-ID: <81b3bc3e-0f6e-ffb3-2b4f-affc6ccf363e@gentoo.org> Date: Wed, 27 May 2020 10:44:16 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 9316ec60-6b6f-4747-9c85-b201cca146d6 X-Archives-Hash: a4c63dabe97be40ad25b899feac35349 On 5/27/20 10:26 AM, Grant Edwards wrote: > I tried to emerge matplotlib today, and it failed because it's linking > in 32-bit libraries instead of 64 bit ones: > > ... > > What would cause that? > On the command-line: -L/usr/lib -L/usr/lib64 Some part of... some build system... is buggy. Those flags can come from many different places: * hard-coded in matplotlib or any of its dependencies' build systems * from a dependency's pkg-config file * incorrectly guessed by a ./configure test that didn't look too hard at which library it found * correctly guessed for a library that was installed to the wrong place (/usr/lib instead of /usr/lib64) Et cetera. Best to file a bug.