From: Arkadiusz Kozdra <floss@arusekk.pl>
To: Nathan Chancellor <nathan@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <nsc@kernel.org>, Jakub Kicinski <kuba@kernel.org>,
Alex Deucher <alexander.deucher@amd.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Mark Brown <broonie@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
Arkadiusz Kozdra <floss@arusekk.pl>
Subject: Re: [PATCH] kconfig: fix static linking of nconf
Date: Mon, 12 Jan 2026 14:24:42 +0100 [thread overview]
Message-ID: <35312d4f-0783-43bf-8a91-0e80bffe821c@arusekk.pl> (raw)
In-Reply-To: <20260110232043.GA90060@ax162>
W dniu 11.01.2026 o 00:20, Nathan Chancellor pisze:
>> -PKG="ncursesw menuw panelw"
>> -PKG2="ncurses menu panel"
> Is it worth a comment that the order of these packages is intentional to
> support static library builds? I do not mind adding after the fact to
> save you from sending a v2. I guess this situation is not too common
> since 1c5af5cf9308 is over six years old at this point but if any other
> dependencies become necessary in the future, it might help folks place
> them in the correct order.
Sure, this is because ld still only visits each archive once,
left-to-right, by design.
I think a comment about library dependencies and order would do a lot.
Feel free to reword and/or add comments as you please.
Thank you for your help.
- Arusekk
next prev parent reply other threads:[~2026-01-12 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 11:48 [PATCH] kconfig: fix static linking of nconf Arkadiusz Kozdra
2026-01-10 23:20 ` Nathan Chancellor
2026-01-12 13:24 ` Arkadiusz Kozdra [this message]
2026-01-14 13:26 ` Nicolas Schier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35312d4f-0783-43bf-8a91-0e80bffe821c@arusekk.pl \
--to=floss@arusekk.pl \
--cc=alexander.deucher@amd.com \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox