Gentoo Archives: gentoo-commits

From: "Andreas K. Hüttel" <dilfridge@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/default/linux/riscv/17.0/rv32imac/ilp32d/, ...
Date: Sat, 25 Sep 2021 21:24:10
Message-Id: 1632605035.a25e7b111a488f60c607212172e5bca73b901890.dilfridge@gentoo
1 commit: a25e7b111a488f60c607212172e5bca73b901890
2 Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
3 AuthorDate: Sat Sep 25 21:23:23 2021 +0000
4 Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
5 CommitDate: Sat Sep 25 21:23:55 2021 +0000
6 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a25e7b11
7
8 profiles: finally deprecate riscv 17.0 profiles, nearly forgot this
9
10 Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
11
12 .../linux/riscv/17.0/rv32imac/ilp32/deprecated | 0
13 .../linux/riscv/17.0/rv32imac/ilp32d/deprecated | 0
14 .../default/linux/riscv/17.0/rv64gc/deprecated | 43 ++++++++++++++++++++++
15 .../linux/riscv/17.0/rv64gc/lp64/deprecated | 43 ++++++++++++++++++++++
16 .../riscv/17.0/rv64gc/lp64/systemd/deprecated | 43 ++++++++++++++++++++++
17 .../linux/riscv/17.0/rv64gc/lp64d/deprecated | 43 ++++++++++++++++++++++
18 .../riscv/17.0/rv64gc/lp64d/systemd/deprecated | 43 ++++++++++++++++++++++
19 7 files changed, 215 insertions(+)
20
21 diff --git a/profiles/default/linux/riscv/17.0/rv32imac/ilp32/deprecated b/profiles/default/linux/riscv/17.0/rv32imac/ilp32/deprecated
22 new file mode 100644
23 index 00000000000..e69de29bb2d
24
25 diff --git a/profiles/default/linux/riscv/17.0/rv32imac/ilp32d/deprecated b/profiles/default/linux/riscv/17.0/rv32imac/ilp32d/deprecated
26 new file mode 100644
27 index 00000000000..e69de29bb2d
28
29 diff --git a/profiles/default/linux/riscv/17.0/rv64gc/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/deprecated
30 new file mode 100644
31 index 00000000000..36128fb4712
32 --- /dev/null
33 +++ b/profiles/default/linux/riscv/17.0/rv64gc/deprecated
34 @@ -0,0 +1,43 @@
35 +default/linux/riscv/20.0/rv64gc/lp64d
36 +
37 +On RISC-V we are switching from two-level library directories (e.g.,
38 +/usr/lib64/lp64d) to a more traditional directory architecture.
39 +This is done via the profile upgrade from 17.0 to 20.0 profiles.
40 +
41 +We recommend to re-install from scratch using a 20.0 profile based
42 +stage. 17.0 profiles will be deprecated immediately and removed
43 +in 6 months.
44 +
45 +If you want to upgrade an existing installation, the following
46 +steps should be taken. Please read all commands carefully first and
47 +make sure you understand them, since the procedure is risky. The
48 +commands are given for a lp64d profile; in case of a lp64 profile,
49 +always replace lp64d with lp64.
50 +
51 +# cd /usr/local/lib64
52 +# cp -av lp64d/. .
53 +# rm -rf lp64d
54 +# ln -s . lp64d
55 +
56 +# cd /usr/lib64
57 +# cp -av lp64d/. .
58 +# rm -rf lp64d
59 +# ln -s . lp64d
60 +
61 +# cd /lib64
62 +# cp -av lp64d/. .
63 +# rm -rf lp64d
64 +# sln . lp64d
65 +
66 +Note that the last command uses "sln" instead of "ln -s".
67 +
68 +Then switch from your 17.0 profile to the corresponding 20.0 profile,
69 +either by using "eselect profile" or by manually changing the
70 +/etc/portage/make.profile symlink.
71 +
72 +Next, rebuild all packages:
73 +
74 +# emerge -eav world
75 +
76 +As last step, check if portage has removed any of the symlinks created
77 +above, and if yes, recreate them.
78
79 diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64/deprecated
80 new file mode 100644
81 index 00000000000..e3804755664
82 --- /dev/null
83 +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64/deprecated
84 @@ -0,0 +1,43 @@
85 +default/linux/riscv/20.0/rv64gc/lp64
86 +
87 +On RISC-V we are switching from two-level library directories (e.g.,
88 +/usr/lib64/lp64d) to a more traditional directory architecture.
89 +This is done via the profile upgrade from 17.0 to 20.0 profiles.
90 +
91 +We recommend to re-install from scratch using a 20.0 profile based
92 +stage. 17.0 profiles will be deprecated immediately and removed
93 +in 6 months.
94 +
95 +If you want to upgrade an existing installation, the following
96 +steps should be taken. Please read all commands carefully first and
97 +make sure you understand them, since the procedure is risky. The
98 +commands are given for a lp64d profile; in case of a lp64 profile,
99 +always replace lp64d with lp64.
100 +
101 +# cd /usr/local/lib64
102 +# cp -av lp64d/. .
103 +# rm -rf lp64d
104 +# ln -s . lp64d
105 +
106 +# cd /usr/lib64
107 +# cp -av lp64d/. .
108 +# rm -rf lp64d
109 +# ln -s . lp64d
110 +
111 +# cd /lib64
112 +# cp -av lp64d/. .
113 +# rm -rf lp64d
114 +# sln . lp64d
115 +
116 +Note that the last command uses "sln" instead of "ln -s".
117 +
118 +Then switch from your 17.0 profile to the corresponding 20.0 profile,
119 +either by using "eselect profile" or by manually changing the
120 +/etc/portage/make.profile symlink.
121 +
122 +Next, rebuild all packages:
123 +
124 +# emerge -eav world
125 +
126 +As last step, check if portage has removed any of the symlinks created
127 +above, and if yes, recreate them.
128
129 diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64/systemd/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64/systemd/deprecated
130 new file mode 100644
131 index 00000000000..70e347cc439
132 --- /dev/null
133 +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64/systemd/deprecated
134 @@ -0,0 +1,43 @@
135 +default/linux/riscv/20.0/rv64gc/lp64/systemd
136 +
137 +On RISC-V we are switching from two-level library directories (e.g.,
138 +/usr/lib64/lp64d) to a more traditional directory architecture.
139 +This is done via the profile upgrade from 17.0 to 20.0 profiles.
140 +
141 +We recommend to re-install from scratch using a 20.0 profile based
142 +stage. 17.0 profiles will be deprecated immediately and removed
143 +in 6 months.
144 +
145 +If you want to upgrade an existing installation, the following
146 +steps should be taken. Please read all commands carefully first and
147 +make sure you understand them, since the procedure is risky. The
148 +commands are given for a lp64d profile; in case of a lp64 profile,
149 +always replace lp64d with lp64.
150 +
151 +# cd /usr/local/lib64
152 +# cp -av lp64d/. .
153 +# rm -rf lp64d
154 +# ln -s . lp64d
155 +
156 +# cd /usr/lib64
157 +# cp -av lp64d/. .
158 +# rm -rf lp64d
159 +# ln -s . lp64d
160 +
161 +# cd /lib64
162 +# cp -av lp64d/. .
163 +# rm -rf lp64d
164 +# sln . lp64d
165 +
166 +Note that the last command uses "sln" instead of "ln -s".
167 +
168 +Then switch from your 17.0 profile to the corresponding 20.0 profile,
169 +either by using "eselect profile" or by manually changing the
170 +/etc/portage/make.profile symlink.
171 +
172 +Next, rebuild all packages:
173 +
174 +# emerge -eav world
175 +
176 +As last step, check if portage has removed any of the symlinks created
177 +above, and if yes, recreate them.
178
179 diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64d/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/deprecated
180 new file mode 100644
181 index 00000000000..36128fb4712
182 --- /dev/null
183 +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/deprecated
184 @@ -0,0 +1,43 @@
185 +default/linux/riscv/20.0/rv64gc/lp64d
186 +
187 +On RISC-V we are switching from two-level library directories (e.g.,
188 +/usr/lib64/lp64d) to a more traditional directory architecture.
189 +This is done via the profile upgrade from 17.0 to 20.0 profiles.
190 +
191 +We recommend to re-install from scratch using a 20.0 profile based
192 +stage. 17.0 profiles will be deprecated immediately and removed
193 +in 6 months.
194 +
195 +If you want to upgrade an existing installation, the following
196 +steps should be taken. Please read all commands carefully first and
197 +make sure you understand them, since the procedure is risky. The
198 +commands are given for a lp64d profile; in case of a lp64 profile,
199 +always replace lp64d with lp64.
200 +
201 +# cd /usr/local/lib64
202 +# cp -av lp64d/. .
203 +# rm -rf lp64d
204 +# ln -s . lp64d
205 +
206 +# cd /usr/lib64
207 +# cp -av lp64d/. .
208 +# rm -rf lp64d
209 +# ln -s . lp64d
210 +
211 +# cd /lib64
212 +# cp -av lp64d/. .
213 +# rm -rf lp64d
214 +# sln . lp64d
215 +
216 +Note that the last command uses "sln" instead of "ln -s".
217 +
218 +Then switch from your 17.0 profile to the corresponding 20.0 profile,
219 +either by using "eselect profile" or by manually changing the
220 +/etc/portage/make.profile symlink.
221 +
222 +Next, rebuild all packages:
223 +
224 +# emerge -eav world
225 +
226 +As last step, check if portage has removed any of the symlinks created
227 +above, and if yes, recreate them.
228
229 diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64d/systemd/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/systemd/deprecated
230 new file mode 100644
231 index 00000000000..cbac179df32
232 --- /dev/null
233 +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/systemd/deprecated
234 @@ -0,0 +1,43 @@
235 +default/linux/riscv/20.0/rv64gc/lp64d/systemd
236 +
237 +On RISC-V we are switching from two-level library directories (e.g.,
238 +/usr/lib64/lp64d) to a more traditional directory architecture.
239 +This is done via the profile upgrade from 17.0 to 20.0 profiles.
240 +
241 +We recommend to re-install from scratch using a 20.0 profile based
242 +stage. 17.0 profiles will be deprecated immediately and removed
243 +in 6 months.
244 +
245 +If you want to upgrade an existing installation, the following
246 +steps should be taken. Please read all commands carefully first and
247 +make sure you understand them, since the procedure is risky. The
248 +commands are given for a lp64d profile; in case of a lp64 profile,
249 +always replace lp64d with lp64.
250 +
251 +# cd /usr/local/lib64
252 +# cp -av lp64d/. .
253 +# rm -rf lp64d
254 +# ln -s . lp64d
255 +
256 +# cd /usr/lib64
257 +# cp -av lp64d/. .
258 +# rm -rf lp64d
259 +# ln -s . lp64d
260 +
261 +# cd /lib64
262 +# cp -av lp64d/. .
263 +# rm -rf lp64d
264 +# sln . lp64d
265 +
266 +Note that the last command uses "sln" instead of "ln -s".
267 +
268 +Then switch from your 17.0 profile to the corresponding 20.0 profile,
269 +either by using "eselect profile" or by manually changing the
270 +/etc/portage/make.profile symlink.
271 +
272 +Next, rebuild all packages:
273 +
274 +# emerge -eav world
275 +
276 +As last step, check if portage has removed any of the symlinks created
277 +above, and if yes, recreate them.