From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BEEA11381F3 for ; Fri, 12 Apr 2013 15:13:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 02767E0881; Fri, 12 Apr 2013 15:13:03 +0000 (UTC) Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by pigeon.gentoo.org (Postfix) with ESMTP id 95E4FE0B47 for ; Fri, 12 Apr 2013 15:13:02 +0000 (UTC) Received: from odin.tremily.us ([unknown] [72.68.100.81]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0ML500409E93LE30@vms173019.mailsrvcs.net> for gentoo-catalyst@lists.gentoo.org; Fri, 12 Apr 2013 10:12:40 -0500 (CDT) Received: by odin.tremily.us (Postfix, from userid 1000) id 88AB096742C; Fri, 12 Apr 2013 11:12:38 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tremily.us; s=odin; t=1365779558; bh=Qp/OHeFb3dpV8eN1J1Db6EyVVmpkub7jtFKOAUsPqnc=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=ClhY7t1XbZoPDX7gVtgILysZ3cmylfH8OelaQ1ZxD13V17aGaKOdmq73s7hwtfnvR vSjIpCT3Qlsx9SYg2cTQKZeKLJdgqKfHE6yEF1IGKyzMaxp0xULrDnlLZdZAG/k7C5 6oJJZS2PZbeo4Sz3+Pc9MwWf/e402Odu63DLIIlE= From: "W. Trevor King" To: Catalyst Cc: "W. Trevor King" Subject: [gentoo-catalyst] [PATCH] files/catalyst.conf: Document linking issues with binary packages Date: Fri, 12 Apr 2013 11:12:34 -0400 Message-id: X-Mailer: git-send-email 1.8.1.5 In-reply-to: <20130411175214.GA14587@odin.tremily.us> References: <20130411175214.GA14587@odin.tremily.us> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org X-Archives-Salt: 13d3064b-597b-4a20-bbde-6f21afe92b69 X-Archives-Hash: 86cc7da9ed3b1e384c6cbcf344bca7c7 From: "W. Trevor King" This gives users a heads up explaining why they might see linking errors when pkgcache is enabled. I first saw this when I build a stage1 without update_seed. Because my seed stage3 linked against libmpc.so.2, some of my stage1 files linked against the older mpc. However, the mpc-1.0.1 built for the stage1 installed libmpc.so.3. When I tried to use this stage1 to build a stage2, it died with: /usr/libexec/gcc/i686-pc-linux-gnu/4.6.3/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory To fix this, I enabled update_seed, but binary packages built during my first pass were used to populate the stage1, so even though I'd updated the seed stage3 toolchain, I still had a stage1 with cc1 linked against libmpc.so.2. After clearing the binary package cache, I got a stage1 *built* with the updated seed stage3, which gave a cc1 linked against libmpc.so.3 (hurray!). This commit adds a warning in the pkgcache documentation that should help people understand what might be going wrong if they see similar linking errors. For more details, see the thread following http://thread.gmane.org/gmane.linux.gentoo.catalyst/2137/focus=2193 --- files/catalyst.conf | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/files/catalyst.conf b/files/catalyst.conf index b74c546..e285e4f 100644 --- a/files/catalyst.conf +++ b/files/catalyst.conf @@ -58,7 +58,11 @@ hash_function="crc32" # kerncache = keeps a tbz2 of your built kernel and modules (useful if your # build stops in livecd-stage2) # pkgcache = keeps a tbz2 of every built package (useful if your build stops -# prematurely) +# prematurely. However, you may see linking problems if the binary +# package was built against an older version of a runtime dependency +# and the package in question is not using EAPI5's sub-slots. For +# further discussion, see +# http://article.gmane.org/gmane.linux.gentoo.catalyst/2224) # seedcache = use the build output of a previous target if it exists to speed up # the copy # snapcache = cache the snapshot so that it can be bind-mounted into the chroot. -- 1.8.2