On 12/03 04:35, Heiko Baums wrote:
> Am Sun, 3 Dec 2017 04:26:55 +0100
> schrieb tu...@posteo.de:
>
> > If the compilation will fail at a certain point (and it will fail,
> > since this is a complete new thing) -- would it be possible to resume
> > even some tweaks, hacks and patches (even certain recompilations)
> > would be needed in between?
>
> Just run `emerge -e --keep-going y @world`.
>
> > Can I stop a running emerge @world and resume later?
>
> Maybe with `emerge --resume`. But I don't know if interrupting this
> would cause some problems in this particular case.
>
> > How does a restarted emerge @world recognizes packages, which are
> > already compiled according to the new standard?
>
> It simply creates a list of the packages to be installed as usual and
> knows which of them are already installed and which are not. Then it
> recalculates the dependency tree as usual.
>
> Heiko
>
Hi Heiko,
...sorry my question was unclear.
Suppose one would do an emerge @world...and then BOOOM! a powerfailyre
would stop the whole thing. Further suppose the filesystem, the
hardware and anything has survived luckily -- only emerge @world needs
to be restarted.
And one does NOT an emerge --resume but an emerge @world.
In this particular case...how does emerge knows from the previous
emerge @world what packages has been recompiled already and are "PIE"?
How can I check, whether a binary is "PIE"-conform ("pie-conform" is
a freaky funny language hack :) ;) ) ?
Cheers
Meino
