Dne 7.7.2015 v 20:26 Jason A. Donenfeld napsal(a):
> Running `make modules_install` ordinarily will overwrite existing
> modules. This is the desired behavior, and is how pretty much every
> other `make install` target works.
>
> However, if CONFIG_MODULE_COMPRESS is enabled, modules are passed
>
Dne 7.7.2015 v 20:26 Jason A. Donenfeld napsal(a):
Running `make modules_install` ordinarily will overwrite existing
modules. This is the desired behavior, and is how pretty much every
other `make install` target works.
However, if CONFIG_MODULE_COMPRESS is enabled, modules are passed
Bump? This should be trivial to merge, and it fixes a really annoying
bug for module development.
On Tue, Jul 7, 2015 at 8:26 PM, Jason A. Donenfeld wrote:
> Running `make modules_install` ordinarily will overwrite existing
> modules. This is the desired behavior, and is how pretty much every
>
Bump? This should be trivial to merge, and it fixes a really annoying
bug for module development.
On Tue, Jul 7, 2015 at 8:26 PM, Jason A. Donenfeld ja...@zx2c4.com wrote:
Running `make modules_install` ordinarily will overwrite existing
modules. This is the desired behavior, and is how pretty
Running `make modules_install` ordinarily will overwrite existing
modules. This is the desired behavior, and is how pretty much every
other `make install` target works.
However, if CONFIG_MODULE_COMPRESS is enabled, modules are passed
through gzip and xz which then do the file writing. Both gzip
Running `make modules_install` ordinarily will overwrite existing
modules. This is the desired behavior, and is how pretty much every
other `make install` target works.
However, if CONFIG_MODULE_COMPRESS is enabled, modules are passed
through gzip and xz which then do the file writing. Both gzip
6 matches
Mail list logo