1 |
10.11.2020 08:55, Fabian Groffen пишет: |
2 |
> On 09-11-2020 19:38:28 +0000, Alexey Sokolov wrote: |
3 |
>> Hi Fabian |
4 |
>> I tried to migrate my prefix to 17.1, and there are issues. |
5 |
>> |
6 |
>> 1) unsymlink-lib requires "--root ~/gentoo" and otherwise produces an |
7 |
>> error "/usr/lib is a real directory! was the migration done already?" |
8 |
> |
9 |
> I think unsymlink-lib doesn't have Prefix support, but in addition, |
10 |
> what unsymlink-lib is trying to achieve, is not a thing perhaps on |
11 |
> Prefix. |
12 |
> |
13 |
> A prefix system (at least all of mine) doesn't have libXX or lib/XX |
14 |
> (a.k.a. multilib) directories. The /usr-split was long ago removed, |
15 |
> and thus what we have is: |
16 |
> |
17 |
> lib -> usr/lib |
18 |
> |
19 |
> Now, SYMLINK_LIB=no seems to split into lib and lib64, but lib64 does |
20 |
> not exist on Prefix systems. |
21 |
> |
22 |
> Since Prefix is non-multilib by design*, I wonder if unsymlink-lib is |
23 |
> necessary in the best case, but going to break the Prefix system in the |
24 |
> worst case. |
25 |
> |
26 |
> What instructed you to perform the migration? Was it the news-item? I |
27 |
> don't think it should apply for Prefix profiles, and perhaps we should |
28 |
> be happy the tool won't work. |
29 |
|
30 |
It was the big scary warning about the deprecation whenever I run |
31 |
emerge. It contains list of steps. |
32 |
|
33 |
> * non-multilib is a decision dating back a decade or so, which means |
34 |
> effectively any Prefix install you encounter should be non-multilib |
35 |
> |
36 |
> |
37 |
>> 2) $ unsymlink-lib --root ~/gentoo --migrate --pretend |
38 |
>> usage: unsymlink-lib [-h] [-p] [--root ROOT] [--analyze] [--migrate] |
39 |
>> [--rollback] [--finish] [--force-rollback] |
40 |
>> [--resume-finish] [-P PREFIX] [--hardlink] |
41 |
>> unsymlink-lib: error: Requested action requires root privileges |
42 |
>> |
43 |
>> Well, I worked it around by adding "is_root = True" to unsymlink-lib |
44 |
> |
45 |
> Did it do anything to your system like creating a lib64 directory? Does |
46 |
> anything work (because I have doubts on whether your system can still |
47 |
> find the libs in there now). |
48 |
|
49 |
Yes. Attaching logs. |
50 |
|
51 |
> |
52 |
>> |
53 |
>> 3) Step 9 (Rebuild gcc) fails: |
54 |
>> configure:4372: checking whether the C compiler works |
55 |
>> |
56 |
>> |
57 |
>> |
58 |
>> configure:4394: x86_64-pc-linux-gnu-gcc conftest.c >&5 |
59 |
>> |
60 |
>> |
61 |
>> |
62 |
>> /home/user/gentoo/usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/as: |
63 |
>> error while loading shared libraries: |
64 |
>> libopcodes-2.34.0.gentoo-sys-devel-binutils-st.so: cannot open shared |
65 |
> |
66 |
> Something like this I was suspecting. Can you still rollback? If you |
67 |
> can, I'd try that and hope it restores your system in working order. |
68 |
|
69 |
Yeah, don't worry, this is my ebuild-testing chroot. I just did "lxc |
70 |
restore". |
71 |
|
72 |
|
73 |
-- |
74 |
Best regards, |
75 |
Alexey "DarthGandalf" Sokolov |