Hi all,
l...@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Mark H Weaver skribis:
>
>> Danny Milosavljevic writes:
>>
>>> On Mon, 16 Jul 2018 18:55:11 +0100 (BST)
>>> wrote:
>>>
It would be good to keep the build directory though, since it's
expected to exist, and it's easier to just d
Hi,
Mark H Weaver skribis:
> Danny Milosavljevic writes:
>
>> On Mon, 16 Jul 2018 18:55:11 +0100 (BST)
>> wrote:
>>
>>> It would be good to keep the build directory though, since it's
>>> expected to exist, and it's easier to just download a module's
>>> source and compile it and test it.
>>
>
Yes I agree with you, since it is a lot of space then it's probably best to
just delete the symlink.
The reasoning behind my suggestion of keeping it is mostly for convenience in
compiling/testing an external kernel module, i.e. just downloading the source
and then compiling it with the current
Danny Milosavljevic writes:
> On Mon, 16 Jul 2018 18:55:11 +0100 (BST)
> wrote:
>
>> It would be good to keep the build directory though, since it's
>> expected to exist, and it's easier to just download a module's
>> source and compile it and test it.
>
> I agree.
>
> /run/booted-system/kernel/
On Mon, 16 Jul 2018 18:55:11 +0100 (BST)
wrote:
> It would be good to keep the build directory though, since it's expected to
> exist, and it's easier to just download a module's source and compile it and
> test it.
I agree.
/run/booted-system/kernel/lib/modules/4.17.3-gnu is in the store any
It would be good to keep the build directory though, since it's expected to
exist, and it's easier to just download a module's source and compile it and
test it.
pki...@runbox.com transcribed 94 bytes:
> /run/booted-system/kernel/lib/modules//build is a broken
> symbolic link.
Yep. This is not a bug until it comes to what you are possibly trying to
attempt,
build a software which relies on your *current* kernel sources.
For a solution I can point to the
/run/booted-system/kernel/lib/modules//build is a broken
symbolic link.
