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 1OVvDI-0005b0-Ht for garchives@archives.gentoo.org; Mon, 05 Jul 2010 23:36:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C0221C077; Mon, 5 Jul 2010 23:35:36 +0000 (UTC) Received: from mxi2.callplus.net.nz (mx194.callplus.net.nz [202.180.66.194]) by pigeon.gentoo.org (Postfix) with ESMTP id 15EAD1C077 for ; Mon, 5 Jul 2010 23:35:35 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai4GAD8JMkx8xQFN/2dsb2JhbACTQIw2cr8ohSUEiDo Received: from 124-197-1-77.callplus.net.nz (HELO vrooom.localnet) ([124.197.1.77]) by ismtp02.callplus.net.nz with ESMTP; 06 Jul 2010 11:35:34 +1200 From: =?iso-8859-1?q?Fran=E7ois_Bissey?= To: gentoo-science@lists.gentoo.org Subject: Re: [gentoo-science] sage-scripts' dependencies Date: Tue, 6 Jul 2010 11:35:33 +1200 User-Agent: KMail/1.13.3 (Linux/2.6.32-gentoo-r7; KDE/4.4.4; i686; ; ) References: <1278349224.27947.0@pavilion64> In-Reply-To: <1278349224.27947.0@pavilion64> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@lists.gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201007061135.34020.f.r.bissey@massey.ac.nz> X-Archives-Salt: 96b68ce2-cd0a-433f-8e06-afd0fc9a5cc0 X-Archives-Hash: aa3d88d875522c099f218b5e4e21d7ab > Hi, > > I encountered the following when making a fresh install of sage (~136 > packages) within a 32bit chroot. Emerge of sage terminated because of the > following line > > dosym $(which gp) "${SAGE_LOCAL}"/bin/sage_pari || die > > in the sage-scripts ebuild. In emerging sage, sage-scripts gets pulled in > before pari and thus the failure. I suppose it would be awkward to have > sage-scripts depend on pari when only a symlink is created? This can be > replicated if one has a working sage by removing pari and sage-scripts and > either updating world or re-emerging sage-core. Here, sage-scripts gets > pulled in before pari and the update/emerge fails. > Hi Steve, I have just added a svn snapshot of pari in the overlay but not all dependencies have been adjusted for the right slot. How did that go? Did you get pari 2.3 or 2.4 installed? I would imagine that if you had only pari 2.4 things failed to compile as I have slotted it so you have to request it explicitly which happens nowhere at the moment. Francois