From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 25 Oct 2023 21:53:53 +0200 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvjwv-003ie0-Vn for lore@lore.pengutronix.de; Wed, 25 Oct 2023 21:53:53 +0200 Received: from localhost ([127.0.0.1] helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1qvjwv-0004VC-2d; Wed, 25 Oct 2023 21:53:53 +0200 Received: from mail.ppc-ag.de ([212.65.2.129]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qvjwi-0004UJ-HZ for ptxdist@pengutronix.de; Wed, 25 Oct 2023 21:53:44 +0200 Received: from [10.40.4.2] (port=53790 helo=masv00063.ppc-ag.de) by mail.ppc-ag.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1qvjwc-0003Q6-08; Wed, 25 Oct 2023 21:53:34 +0200 Received: from localhost (localhost [127.0.0.1]) by masv00063.ppc-ag.de (Postfix) with ESMTP id EDCA41E917B4; Wed, 25 Oct 2023 21:53:33 +0200 (CEST) Received: from masv00063.ppc-ag.de ([127.0.0.1]) by localhost (masv00063.ppc-ag.de [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 54smfDF1JB2d; Wed, 25 Oct 2023 21:53:33 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by masv00063.ppc-ag.de (Postfix) with ESMTP id A22FC1E91D6E; Wed, 25 Oct 2023 21:53:33 +0200 (CEST) X-SASI-Hits: BODY_SIZE_3000_3999 0.000000, BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000, CTE_QUOTED_PRINTABLE 0.000000, HTML_00_01 0.050000, HTML_00_10 0.050000, IN_REP_TO 0.000000, LEGITIMATE_SIGNS 0.000000, MSG_THREAD 0.000000, MULTIPLE_REAL_RCPTS 0.000000, NO_CTA_URI_FOUND 0.000000, NO_FUR_HEADER 0.000000, NO_URI_HTTPS 0.000000, OUTBOUND 0.000000, OUTBOUND_SOPHOS 0.000000, REFERENCES 0.000000, SENDER_NO_AUTH 0.000000, SUPERLONG_LINE 0.050000, SUSP_DH_NEG 0.000000, __ANY_URI 0.000000, __BODY_NO_MAILTO 0.000000, __BOUNCE_CHALLENGE_SUBJ 0.000000, __BOUNCE_NDR_SUBJ_EXEMPT 0.000000, __BULK_NEGATE 0.000000, __CC_NAME 0.000000, __COURIER_PHRASE 0.000000, __CP_MEDIA_BODY 0.000000, __CT 0.000000, __CTE 0.000000, __CT_TEXT_PLAIN 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FORWARDED_MSG 0.000000, __FRAUD_REFNUM 0.000000, __FRAUD_URGENCY 0.000000, __FUR_RDNS_SOPHOS 0.000000, __HAS_CC_HDR 0.000000, __HAS_FROM 0.000000, __HAS_MSGID 0.000000, __HAS_REFERENCES 0.000000, __HAS_X_MAILER 0.000000, __HELO_LOCALHOST 0.000000, __HIGHBIT_ASCII_MIX 0.000000, __INVOICE_MULTILINGUAL 0.000000, __IN_REP_TO 0.000000, __IOC_PHRASE 0.000000, __MAIL_CHAIN 0.000000, __MIME_BOUND_CHARSET 0.000000, __MIME_TEXT_ONLY 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_VERSION 0.000000, __NO_HTML_TAG_RAW 0.000000, __OUTBOUND_SOPHOS_FUR 0.000000, __OUTBOUND_SOPHOS_FUR_IP 0.000000, __OUTBOUND_SOPHOS_FUR_RDNS 0.000000, __RCVD_FROM_DOMAIN 0.000000, __RCVD_FROM_SUSP_HOSTNAME 0.000000, __REFERENCES 0.000000, __SANE_MSGID 0.000000, __SCAN_D_NEG 0.000000, __SCAN_D_NEG2 0.000000, __SCAN_D_NEG_HEUR 0.000000, __SCAN_D_NEG_HEUR2 0.000000, __SUBJ_ALPHA_NEGATE 0.000000, __SUBJ_ENDS_IN_DATE 0.000000, __SUBJ_REPLY 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_HAS_HYPHEN_USC 0.000000, __URI_MAILTO 0.000000, __URI_NO_WWW 0.000000, __URI_NS 0.000000, __X_MAILER_ZIMBRA 0.000000, __X_VIRUS_SCANNED 0.000000 X-SASI-Probability: 8% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 5.1.4, AntispamData: 2023.10.25.190917 X-Virus-Scanned: amavisd-new at masv00063.ppc-ag.de Received: from masv00063.ppc-ag.de ([127.0.0.1]) by localhost (masv00063.ppc-ag.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ItvJ5iEvCIOX; Wed, 25 Oct 2023 21:53:33 +0200 (CEST) Received: from masv00063.ppc-ag.de (localhost [127.0.0.1]) by masv00063.ppc-ag.de (Postfix) with ESMTP id 9059E1E917B4; Wed, 25 Oct 2023 21:53:33 +0200 (CEST) Date: Wed, 25 Oct 2023 21:53:33 +0200 (CEST) From: Mircea Ciocan To: christian melki Message-ID: <793465806.493628.1698263613576.JavaMail.zimbra@ppc-ag.de> In-Reply-To: References: <825314430.404032.1698241702676.JavaMail.zimbra@ppc-ag.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 8.8.15_GA_4545 (ZimbraWebClient - FF118 (Linux)/8.8.15_GA_4545) Thread-Topic: util-linux fail to compile with 2023.10.0 Thread-Index: 696ivStxAT7r3A4LziklPaHIO8x2Zg== X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.whiteo.stw.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-1.9 required=4.0 tests=AWL,BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] util-linux fail to compile with 2023.10.0 X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Cc: ptxdist Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false ----- Urspr=C3=BCngliche Mail ----- Von: "Christian Melki" An: "Mircea Ciocan" CC: "ptxdist" Gesendet: Mittwoch, 25. Oktober 2023 21:38:18 Betreff: Re: [ptxdist] util-linux fail to compile with 2023.10.0 On 10/25/23 15:48, Mircea Ciocan wrote: > Hello list, >=20 > while attempting to compile ptxdist with 2023.10.0 I've encountered a fai= lure in cfdisk package, that is build regardless if it is selected or not i= n the ptxconfig :(, no one seems to use PTXCONF_UTIL_LINUX_CFDISK to select= if the cfdisk utility is build or not, Hi! This is is what I see: CFDISK is a separate flag that sets FDISKS. FDISKS is then used to build all fdisks. But only the selected fdisks get installed. I don't see an error here? but unfortunately if also no other packages that use the ncurses library are also not selected, when cfdisk is compiled the following error occurs: Do I understand it correctly when you say that the only user of ncurses in your entire build is cfdisk? Seems quite odd, hence my rather stupid question. In that case, can you please check that NCURSES actually gets built before util-linux? And that your selected ptxconfig contains ncurses? >=20 > [479/612] Linking target cfdisk > FAILED: cfdisk=20 > /opt/OSELAS.Toolchain-2023.07.0/arm-v7a-linux-gnueabihf/gcc-13.2.0-clang-= 17.0.1-glibc-2.37-binutils-2.41-kernel-6.1-sanitized/lib/gcc/arm-v7a-linux-= gnueabihf/13.2.0/../../../../arm-v7a-linux-gnueabihf/bin/ld: platform-dabij= a/build-target/util-linux-2.39.2-build/../util-linux-2.39.2/disk-utils/cfdi= sk.c:685:(.text+0x50): undefined reference to `wclrtoeol' > /opt/OSELAS.Toolchain-2023.07.0/arm-v7a-linux-gnueabihf/gcc-13.2.0-clang-= 17.0.1-glibc-2.37-binutils-2.41-kernel-6.1-sanitized/lib/gcc/arm-v7a-linux-= gnueabihf/13.2.0/../../../../arm-v7a-linux-gnueabihf/bin/ld: platform-dabij= a/build-target/util-linux-2.39.2-build/../util-linux-2.39.2/disk-utils/cfdi= sk.c:697:(.text+0xae): undefined reference to `wattr_on' > [...snip many more similar messages...] >=20 > Maybe the maintainer of the package will have a look, because I think the= re may be some other packages that are not actually constrained with the pt= xconf selection options. >=20 I couldn't reproduce this in 09 or 10. x86_64 or arm-v7a. Now I don't have an ncurses cfdisk only build nor do I have OSELAS as toolchain. I don't think the latter should make much of a difference though. Our toolchain for arm-v7a looks rather similar in components. Regards, Christian > Best regards, > Mircea > Thanks for the answer Christian, I'm at home now, but I remember that there= were actually three sub-packages of util-linux that were selecting ncurses= , in my configuration, by chance, none of them was selected and no other pa= ckages in the whole configuration are using ncurses, as my device is fully = headless, there is no need for it. The problem is that cfdisk can be individually de-selected in menuconfig, b= ut still it is build, if is actually installed in the fw image even if dese= lected, this I don't know, I can test if you like. Would be nice if cfdisk (and other parts of util-linux that can be individu= ally deselected in the configuration menu) could be inhibited to be build a= t all when not selected, I don't know if is possible as an util-linux confi= guration parameter. Right now, if I select cfdisk in the configuration menu, the build succeeds= but I have yet another library that I don't need as well as anotother usel= ess utility (for the specific use case). I really don't know how to solve this, and I will be happy to learn from th= is, the whole Meson crazyness is still new to me. BTW, the previous release set of rules are working, but I believe these are= still autoconf based. Best regards, Mircea