1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 07/05/2013 09:41 PM, Ryan Hill wrote: |
5 |
> On Fri, 05 Jul 2013 15:47:08 -0400 |
6 |
> "Rick \"Zero_Chaos\" Farina" <zerochaos@g.o> wrote: |
7 |
> |
8 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
9 |
>> Hash: SHA1 |
10 |
>> |
11 |
>>> Paweł was nice enough to write a patch for us to get toolchain.eclass up to |
12 |
>>> EAPI 5. I believe it still needs some pieces like prefix support and I |
13 |
>>> haven't reviewed it in depth but it looks good so far (and much simpler |
14 |
>>> than I thought (oops)). I'm planning on moving up an EAPI at a time, |
15 |
>>> bumping it whenever we could use new features or people start hucking fruit. |
16 |
>>> |
17 |
>>> |
18 |
>> I would be forever in your debt if toolchain were on eapi 5 and had |
19 |
>> proper subslot deps. |
20 |
> |
21 |
> What use case are you encountering? I hadn't planned on using subslots, but |
22 |
> I'm open to good reasons/bribery. |
23 |
> |
24 |
> |
25 |
|
26 |
Livecd builds work like this: |
27 |
|
28 |
stage3 tarball is unpacked, then toolchain (minimum package set) is |
29 |
built with ROOT=/tmp/stage1root and is linked to the original (seed |
30 |
stage) while being built. |
31 |
|
32 |
When we then move onto stage 2, it uses just the packages built during |
33 |
stage1 (/tmp/stage1root becomes /). This means, if seed stage has |
34 |
mpc.so.0.1 but portage has since included mpc.so.2 that the gcc in |
35 |
stage2 is linked against mpc.so.0.1 but only mpc.so.0.2 is installed. |
36 |
|
37 |
To combat this kind of failure we are currently running "emerge --update |
38 |
- --deep --newuse --complete-graph --rebuild-if-new-ver gcc" which could |
39 |
just be "emerge --update gcc" if eapi 5 subslots were used properly. |
40 |
|
41 |
Please forgive me if any of these details aren't perfect, I'm using my |
42 |
best recollection of the most recent issue which happened when mpc was |
43 |
bumped a few months ago. |
44 |
|
45 |
I am available on irc quite a bit if you would like to discuss, however, |
46 |
if you want to keep it on the ML we really need to move this to -dev. |
47 |
|
48 |
Thanks, |
49 |
Zero |
50 |
-----BEGIN PGP SIGNATURE----- |
51 |
Version: GnuPG v2.0.19 (GNU/Linux) |
52 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
53 |
|
54 |
iQIcBAEBAgAGBQJR136KAAoJEKXdFCfdEflK1AcP/0uYADFi6lso1df+Us+Cq6T7 |
55 |
dKookGsH04P9ToOGttn4otZC0a0vYTtvYF45Ez9y+SnU5ra3jWV0TwjdTU1t+wUc |
56 |
h7e/h9zlU2Vls/OskdnbwRdTzZACLd5feLzkAjfBrqGtSipi7gKqnyC/6eEaNuQJ |
57 |
Tbv7fS8luNIgNyPA87EbVst3TR5ruKehjDwEOECYmuX9MicUO0m6uPmaO6O4xtbe |
58 |
A1fmkbdvZqPKROnvUBOJPxGrMYWqvL3Z7qcl0bjDK/GOL8tudGPUvRLMf10auIu7 |
59 |
apfpLsv2xeDD0E4u+jx4+Z1mrS2g+L+11d6yz8cNhiduedcHfJKF+pkhTiHEXvzX |
60 |
7RxSqq5jKfqW7nh+ACm1I7cLcioV+e6BIXYcp4sQnkoAIXy6D0bMm6ZdXpqDizI4 |
61 |
Zz8VMc+vyNKyhLB7g8L+34RX38wTc8DNDaXDHV7PCNsuj6JtMtXj0zCkkIlEUo9V |
62 |
bHSX4jvXGGvMV9Bmih/91/69MieCgi2U6a0t4838KHdBxE7tg/3SET1a1axLNYAD |
63 |
YsuHFaqDYXhmxjDywGBLD6XtReAOjhDnrRthc2kp6Oy5YeOwcl/k5ZV/ruYmA/m0 |
64 |
0ZfewBr+O2UTtLBqvKy1JVbxxeKWXKOzH7HdOfiLH90yDMIb63BNM++hKoMRFX3R |
65 |
wqyiBLCnBevVjxF7jN7v |
66 |
=8dF7 |
67 |
-----END PGP SIGNATURE----- |