1 |
On Sun, 24 May 2020 09:40:50 +0800 |
2 |
"Pengcheng Xu" <i@××××××××.moe> wrote: |
3 |
|
4 |
> > USE=-native-symlinks removes a bunch of links that most packages use by default |
5 |
> > until are overridden explicitly. Incomplete list is: |
6 |
> > - /lib/cpp |
7 |
> > - /usr/bin/{gcc,cc,g++,c++,...} |
8 |
> > - /usr/bin/{as,ld,ranlib,dwp,...} |
9 |
> > |
10 |
> > The rule of thumb is: if a tool does not have ${CTARGET}- prefix it will probably |
11 |
> > disappear with USE=-native-symlinks. |
12 |
> > |
13 |
> > (At least eventually) 'emerge' should still be able to build most of packages |
14 |
> > in such environment. I expect initial breakage will be huge though. |
15 |
> > |
16 |
> > Using './configure && make && make install' style workflow will be more tedious. |
17 |
> > One workaround at least for gcc is to use something like: |
18 |
> > $ PATH="$(gcc-config -B):$PATH" |
19 |
> > It's not perfect. We'll see if toolchain can provide nicer environment. |
20 |
> > |
21 |
> |
22 |
> Do we currently have (or is there a plan for) a mechanism to manage the symbolic links and/or create them after merging the package when necessary? It's quite tiresome to type in $CHOST-gcc for simple everyday tasks. |
23 |
|
24 |
There currently is no nice way to get stable path with up-to-date |
25 |
symlinks for current gcc/binutils. I think of adding a gentoo-specific |
26 |
directory to manage symlinks similar to what 'gcc-config -B' provides |
27 |
in a stable path that you can write once into user's PATH. |
28 |
|
29 |
No concrete implementation yet. Filed https://bugs.gentoo.org/724980 |
30 |
to track it. |
31 |
|
32 |
-- |
33 |
|
34 |
Sergei |