> USE=-native-symlinks removes a bunch of links that most packages use by
> default
> until are overridden explicitly. Incomplete list is:
> - /lib/cpp
> - /usr/bin/{gcc,cc,g++,c++,...}
> - /usr/bin/{as,ld,ranlib,dwp,...}
>
> The rule of thumb is: if a tool does not have ${CTARGET}- prefix it will
> probably
> disappear with USE=-native-symlinks.
>
> (At least eventually) 'emerge' should still be able to build most of packages
> in such environment. I expect initial breakage will be huge though.
>
> Using './configure && make && make install' style workflow will be more
> tedious.
> One workaround at least for gcc is to use something like:
> $ PATH="$(gcc-config -B):$PATH"
> It's not perfect. We'll see if toolchain can provide nicer environment.
> 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. Regards, -- Pengcheng Xu https://jsteward.moe
openpgp-digital-signature.asc
Description: PGP signature
