| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 04/12/2013 11:12 AM, W. Trevor King wrote: |
| 5 |
> From: "W. Trevor King" <wking@×××××××.us> |
| 6 |
> |
| 7 |
> This gives users a heads up explaining why they might see linking |
| 8 |
> errors when pkgcache is enabled. I first saw this when I build a |
| 9 |
> stage1 without update_seed. Because my seed stage3 linked against |
| 10 |
> libmpc.so.2, some of my stage1 files linked against the older mpc. |
| 11 |
> However, the mpc-1.0.1 built for the stage1 installed libmpc.so.3. |
| 12 |
> When I tried to use this stage1 to build a stage2, it died with: |
| 13 |
> |
| 14 |
> /usr/libexec/gcc/i686-pc-linux-gnu/4.6.3/cc1: |
| 15 |
> error while loading shared libraries: libmpc.so.2: |
| 16 |
> cannot open shared object file: No such file or directory |
| 17 |
> |
| 18 |
> To fix this, I enabled update_seed, but binary packages built during |
| 19 |
> my first pass were used to populate the stage1, so even though I'd |
| 20 |
> updated the seed stage3 toolchain, I still had a stage1 with cc1 |
| 21 |
> linked against libmpc.so.2. |
| 22 |
> |
| 23 |
> After clearing the binary package cache, I got a stage1 *built* with |
| 24 |
> the updated seed stage3, which gave a cc1 linked against libmpc.so.3 |
| 25 |
> (hurray!). |
| 26 |
> |
| 27 |
> This commit adds a warning in the pkgcache documentation that should |
| 28 |
> help people understand what might be going wrong if they see similar |
| 29 |
> linking errors. For more details, see the thread following |
| 30 |
> http://thread.gmane.org/gmane.linux.gentoo.catalyst/2137/focus=2193 |
| 31 |
|
| 32 |
NACK. Personally I love this idea but I'm really against having a link |
| 33 |
to a ML discussion, no one is going to quit configuring catalyst in the |
| 34 |
middle to read a ML discussion... |
| 35 |
|
| 36 |
- -ZC |
| 37 |
> --- |
| 38 |
> files/catalyst.conf | 6 +++++- |
| 39 |
> 1 file changed, 5 insertions(+), 1 deletion(-) |
| 40 |
> |
| 41 |
> diff --git a/files/catalyst.conf b/files/catalyst.conf |
| 42 |
> index b74c546..e285e4f 100644 |
| 43 |
> --- a/files/catalyst.conf |
| 44 |
> +++ b/files/catalyst.conf |
| 45 |
> @@ -58,7 +58,11 @@ hash_function="crc32" |
| 46 |
> # kerncache = keeps a tbz2 of your built kernel and modules (useful if your |
| 47 |
> # build stops in livecd-stage2) |
| 48 |
> # pkgcache = keeps a tbz2 of every built package (useful if your build stops |
| 49 |
> -# prematurely) |
| 50 |
> +# prematurely. However, you may see linking problems if the binary |
| 51 |
> +# package was built against an older version of a runtime dependency |
| 52 |
> +# and the package in question is not using EAPI5's sub-slots. For |
| 53 |
> +# further discussion, see |
| 54 |
> +# http://article.gmane.org/gmane.linux.gentoo.catalyst/2224) |
| 55 |
> # seedcache = use the build output of a previous target if it exists to speed up |
| 56 |
> # the copy |
| 57 |
> # snapcache = cache the snapshot so that it can be bind-mounted into the chroot. |
| 58 |
> |
| 59 |
|
| 60 |
-----BEGIN PGP SIGNATURE----- |
| 61 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 62 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 63 |
|
| 64 |
iQIcBAEBAgAGBQJRaCZdAAoJEKXdFCfdEflKpe4QAKsr4Ct1zch9TXFe4E9575HP |
| 65 |
YnyScCSgKO8ed9/SfvvNu42GlFAdVbA/awvRqEvSPSrdzTQB0tb0aw5O4daciT98 |
| 66 |
tLoO6y5YHyOk7bsoEtvmAJVZgHcApGgs9MfjUNkTObS6VzYInBYccFxPOjfefy6C |
| 67 |
GoK/hfR1RaUlCPgopaTS8JSWBQyTNjzX7O/CrW4b5RGMMXanX1+X3SVI/75Qg8Ux |
| 68 |
8HxcuK5IPRyAUFAw4HIyIPMNAzv/v4FRfbGMBsjYApeE0HP+kMb953VfRJ0jSuNH |
| 69 |
DvukXwuwHcR704FUjD2TsN7XG/LdLZB/1jQSv/h2w8XkINQpW5M6J6TJjiGx1CyS |
| 70 |
o1CefuyPL9PRzRv7vpN7HsmxPnBkezoLu7xoafzezdrgI6FBM1jXIC2Up4R8GTR7 |
| 71 |
Hgzf7kiC+HTXB/YQIscSze/5M1Rl+fk+O6ycfn5w9Sy5t3XEB417u55pDRPUiUFi |
| 72 |
wtvrbchf7mTfvo95iWeXt3vGbUaA1EbdW4Z95A5HPS8QvlXmnoeN2DHhO58pisMa |
| 73 |
WCTTq3JyQxrNwoTHcukaSGsHzKbzOYXkM1X+/UfxCdQIACiHstkJkRSidYnKsIEp |
| 74 |
2ZfleRxg4WdrTiqnOofknOoHofkssLHx19s0QYTgIBVL5mirAJhB8Oyz5KPXif9F |
| 75 |
QGAqhASyVtzxuIIXKJjE |
| 76 |
=Uv3R |
| 77 |
-----END PGP SIGNATURE----- |
Archives