[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNASDi7RTBk6z4=J8mtyoRd7-NKD36d2fGwtkA_=tdmka0g@mail.gmail.com>
Date: Thu, 24 Aug 2023 10:44:29 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: linux-kbuild@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>
Subject: Re: [PATCH] kbuild: get lib-y objects back to static library
On Thu, Aug 24, 2023 at 10:05 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> Revert the following two commits:
>
> - 7273ad2b08f8 ("kbuild: link lib-y objects to vmlinux forcibly when CONFIG_MODULES=y")
> - 7f2084fa55e6 ("[kbuild] handle exports in lib-y objects reliably")
>
> Now, lib-y is back to static library again, and the link order is
> consistent w/wo CONFIG_MODULES.
>
> Since commit ddb5cdbafaaa ("kbuild: generate KSYMTAB entries by
> modpost"), .vmlinux.export.c contains references to exported symbols.
> If a symbol in a lib-y object is exported, that object is always linked
> even without any explicit user in vmlinux.
>
> Signed-off-by: Masahiro Yamada <masahiroy@...nel.org>
> ---
I just recalled that presumably ARM code must be fixed beforehand.
https://lore.kernel.org/lkml/20230619143725.57967-1-masahiroy@kernel.org/
$(mmu-y) is added to lib-y, but they cannot go into a static library.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists