[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUVnrNJ2=LYF_mre6npUvGHP8xAxdAAipLN_sQEvsK0wmg@mail.gmail.com>
Date: Fri, 9 Apr 2021 12:30:56 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Piotr Gorski <lucjan.lucjanov@...il.com>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
masahiroy@...nel.org, oleksandr@...alenko.name
Subject: Re: Subject: Re: [PATCH v3] kbuild: add support for zstd compressed modules
On Thu, Apr 8, 2021 at 11:05 PM Piotr Gorski <lucjan.lucjanov@...il.com> wrote:
>
> No, the --rm option is essential. xz and gzip have the --rm option built in as opposed to zstd, which is why I used it. I've been using zstd module compression since last december (although I set a different compression level on mine) and everything works fine. Oleksandr also tested it at his place and didn't report any objections.
[ CC me I am not subscribed to linux-kbuild or linux-kernel ]
[ CC Nick ]
Unfortunately, I do not find my initial posting which has all information.
I add the link to the thread on linux-kbuild ML.
So, I gave you as much information as I have (linux-config, make-line
etc.) and you write "everything works fine"?
What do you mean by "everything" - different compressors and none?
Is that working "fine"?
What build environment do you use?
Here: Debian/testing AMD64.
Did you try with...
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_INFO_DWARF5=y
CONFIG_MODULE_COMPRESS_ZSTD=y
...Kconfigs enabled?
As said I use builddeb from scripts directory to generate my Debian packages.
Any chance you can test with builddeb?
I have enabled Clang-LTO Kconfig.
Tried with Clang-LTO Kconfig?
This worked *before* and *after*...
kbuild: add support for zstd compressed modules
kbuild: remove CONFIG_MODULE_COMPRESS (CC Nick as he is listed as a
reviewer here)
... not within my build-environment.
For me this is a *regression*.
- Sedat -
[1] https://marc.info/?t=161790914600002&r=1&w=2
Powered by blists - more mailing lists