Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <b56a03b8-2a2a-f833-a5d2-cdc50a7ca2bb@cschramm.eu>
Date:   Wed, 4 Jan 2023 09:12:35 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
To:     masahiroy@kernel.org, samuel@sholland.org, nathan@kernel.org
Cc:     linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
        ndesaulniers@google.com, nicolas@fjasle.eu
References: <CAK7LNAQc-gEY_v-5f99r=Zeq0oQ3R7apdrc-3M14akhHBp_GoA@mail.gmail.com>
Content-Language: en-US
From:   Christopher Schramm <debian@cschramm.eu>
In-Reply-To: <CAK7LNAQc-gEY_v-5f99r=Zeq0oQ3R7apdrc-3M14akhHBp_GoA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PATCH] kbuild: Fix running modpost with musl libc
Precedence: bulk

This change seems to break expected symbol warnings when building an 
external module against a kernel prepared with modules_prepare.

The build used to show

     WARNING: Module.symvers is missing.
              Modules may not have dependencies or modversions.
              You may get many unresolved symbol warnings.

followed by those many unresolved symbol warnings.

6.2-rc2 still shows that warning but the unresolved symbol messages are 
now errors and the build fails (at scripts/Makefile.modpost:137). This 
seems to happen due to -T getting added.