On Sat, Sep 12, 2020 at 10:12:53PM -0400, John Covici wrote:
> Just in case anyone runs into this problem, I solved by making sure my
> umask was set to 002 and then I unmerged and re-emerged the kernel and
> recompiled and all was well.
It seems like re-emerging is the common solution here [1],
On Fri, 11 Sep 2020 21:48:45 -0400,
Ashley Dixon wrote:
>
> [1 ]
> On Fri, Sep 11, 2020 at 09:42:25PM -0400, John Covici wrote:
> > So, I then tried to do emerge @module-rebuild and got strange results. I
> > get
> > when emerging wireguard endlessly repeated lines like the following:
> > #
On Fri, 11 Sep 2020 21:48:45 -0400,
Ashley Dixon wrote:
>
> [1 ]
> On Fri, Sep 11, 2020 at 09:42:25PM -0400, John Covici wrote:
> > So, I then tried to do emerge @module-rebuild and got strange results. I
> > get
> > when emerging wireguard endlessly repeated lines like the following:
> > #
On Fri, Sep 11, 2020 at 09:42:25PM -0400, John Covici wrote:
> So, I then tried to do emerge @module-rebuild and got strange results. I get
> when emerging wireguard endlessly repeated lines like the following:
> # Do not try to update included dependency files
> and when I try to emerge
Hi. I am having problems doing emerge @module-rebuild to update my
kernel to linux-4.19.144-gentoo. I copied my previous .config from
128-gentoo, did make oldconfig then did make bzimage, modules and
modules_install without problems. So, I then tried to do emerge
@module-rebuild and got strange
5 matches
Mail list logo