Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 131CB22365B for <~alpine/devel@lists.alpinelinux.org>; Fri, 26 Dec 2025 16:40:52 +0000 (UTC) Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 55B2A240027 for <~alpine/devel@lists.alpinelinux.org>; Fri, 26 Dec 2025 17:40:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.net; s=2017; t=1766767252; bh=ufxfDmwkMwkjnX0bATrw3QEl5yxJsraiiR3KoLSfuGs=; h=Mime-Version:Content-Transfer-Encoding:Content-Type:Date: Message-Id:Cc:Subject:From:To:From; b=F5p9PYGaxjVQmSkYw5yYFSZT7Abl+kiQbPOcDmEHtBiEkJJ3mDaqhmpSJn52+dP3I KhAuSlG9UtLIIFfSENp/to6uzwsqL84LI7UCTXqpv64/V1tkDEV4ZaePgXn8L4+slh Q+gfyHzwNWQRG5dMzZVN0iLuEWNjDed6rCmAJUb6K67gVJRFAFTdu29Z5g0XpIY7q0 sH4xaqn3INsImfleZIZts7SpQQYOLLvEiRqxTvPHaddDIeXoWqHjC2YrErajEKvXdd RG0V26t0bFmEHaRJpyn486u6f3qhc/DF5HX+RxCh+1CgEKtIN3jMR1q4nmvfm+koT8 cu1JOnjwOciJA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4ddBFH4vBjz9rxL; Fri, 26 Dec 2025 17:40:51 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 26 Dec 2025 16:40:51 +0000 Message-Id: Cc: "~alpine/devel" <~alpine/devel@lists.alpinelinux.org> Subject: Re: under x86_64, bootstrap i486 build. stopped at lua5.5 dependency From: "Sertonix" To: =?utf-8?q?=E5=B0=A4=E6=99=93=E6=9D=B0?= , "Sertonix" References: <5fe45fe5.90f5.19b5a3c59c0.Coremail.yxj790222@163.com> In-Reply-To: On Fri Dec 26, 2025 at 5:10 PM CET, =E5=B0=A4=E6=99=93=E6=9D=B0 wrote: > thanks for your patience. just switch debian to arch and alpine. After > your explanation I see using 3.23.2 stable to build git master, this > is the reason of this error. if I upgrade to edge, should it be ok? There could be some soname issues when upgrading CBUILD while bootstrapping but otherwise it should be ok. > the unpatched authentic kernel could be compiled with musl lib > successfully? the other expression is whether kernel and the lib we > take has conecxion. we need modify kernel to adopt to musl? I suspect > most of the patches of kernel is for such purpose. The kernel does not need patches for musl libc. Both glibc and musl libc use the same kernel interfaces without modifications.