From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) by sourceware.org (Postfix) with ESMTPS id 4760A385380B for ; Mon, 31 Oct 2022 15:10:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 4760A385380B Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=foss.st.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=foss.st.com Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 29VErNCb020184 for ; Mon, 31 Oct 2022 16:10:45 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=message-id : date : mime-version : subject : to : references : from : in-reply-to : content-type : content-transfer-encoding; s=selector1; bh=vQwtnH5pj0Ac4TyRccXpJ/5EL55br1q7RYMMla6LHfg=; b=Xz93SAHXPIS6PkqkajCqMrkwn7atIMlGwcFM6fuMVRqWPqPekyFSHbgglNRejH631sGG MI7P0/bPeiAqLQJuk+FU7ccEmjoWNUMUOHGAmlPR0eASlOTLBmq9yLpwmQKFih/4iZqS yZ49mxjEY2DVuWG7mWFWydnaqfL5a5Al7YE6gqVvnHqImlij7K+JzCgYOiwLnJigV1T8 9ui9v+2uk91L/QiMYFLMGTotz1Kl6lwhgTIL+bd7MivoJg4aAdszelQ7L/QV/kpQwdAD cwikLP/8uphAusVOzED7+8DRs+mlttIQasFGeP2NlHrEr7pxN0nuvw119PZ1xF2Yjl0G rg== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3kgvct3u3b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 31 Oct 2022 16:10:45 +0100 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 35B1310002A for ; Mon, 31 Oct 2022 16:10:39 +0100 (CET) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id EF7CE22A6D8 for ; Mon, 31 Oct 2022 16:10:39 +0100 (CET) Received: from [10.252.5.166] (10.252.5.166) by SHFDAG1NODE3.st.com (10.75.129.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 31 Oct 2022 16:10:37 +0100 Message-ID: Date: Mon, 31 Oct 2022 16:10:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: Generate porting.info in build tree rather than source tree Content-Language: en-US To: References: <123f7625-98be-a5ee-40c7-f743dbc326fa@foss.st.com> <407c1d77-494e-b091-3390-4e8415631056@foss.st.com> From: Torbjorn SVENSSON In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.252.5.166] X-ClientProxiedBy: EQNCAS1NODE4.st.com (10.75.129.82) To SHFDAG1NODE3.st.com (10.75.129.71) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.545,FMLib:17.11.122.1 definitions=2022-10-31_17,2022-10-31_01,2022-06-22_01 X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2022-10-30 08:12, Mike Frysinger wrote: > On 29 Oct 2022 17:38, Torbjorn SVENSSON wrote: >> Okay, so in that case, something changed in the newlib build process to >> generate and install the porting.info file > > porting.info is part of libgloss, not newlib. i understand the source tarball > is packaged overall as "newlib" so it can be a little confusing. > > older versions build & install porting.info if you use the install-info target. > but it wouldn't do it by default. Might be so, but not for the default make target (the one I used). What make target should I use to build everything, just like the build system did before your improvement, but avoid the .info files? >> as it was not required in the >> Arm snapshot included in their 10.3-2021.10 release (commit >> 2a3a03972b35377aef8d3d52d873ac3b8fcc512c in newlib tree). >> >> You can find the source tree of the 10.3-2021.10 release here: >> https://developer.arm.com/-/media/Files/downloads/gnu-rm/10.3-2021.10/gcc-arm-none-eabi-10.3-2021.10-src.tar.bz2 > > i'm not super interested in random vendor drops, so i won't bother looking. It was just used as a reference to where I got the commands from, so no need to check the tarball if you don't want to. >> Please note that I do get porting.info, but not libc.info, libm.info or >> any other .info files in my build. I suppose a build should generate all >> .info files or none from the source tree? > > newlib calls AM_INIT_AUTOMAKE(no-installinfo). this is a holdover from when > newlib was using AM_INIT_AUTOMAKE(cygnus) which implies no-installinfo. > > libgloss has never used cygnus nor no-installinfo with automake. but it also > wasn't really using automake files in subdirs (like the doc/ dir). and the > hand-written libgloss doc/Makefile.in didn't build+install it by default. so > when i converted it to automake, that was subtly enabled by default. > > imo we should have these enabled by default in newlib for libc & libm as it > aligns with the GNU project standards. anyone shipping releases should have > the info pages includes so end devs don't generate it themselves. if you're > building from git, then having extra tools is kind of expected. > -mike My main concern is that these .info files were treated differently and that the 2 builds produced different file sets. Anyway, I saw your patch and I think it makes more sense to have all files, or none that some of them. It would be nice if this was an option to the build system, but I suppose that would require some more work/time.