From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx07-00178001.pphosted.com (mx07-00178001.pphosted.com [185.132.182.106]) by sourceware.org (Postfix) with ESMTPS id 57461385D0D0 for ; Fri, 28 Oct 2022 15:41:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 57461385D0D0 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 (m0288072.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 29SD4LFH008626; Fri, 28 Oct 2022 17:40:53 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=message-id : date : mime-version : to : from : subject : cc : content-type : content-transfer-encoding; s=selector1; bh=SND0ni82Bqljv0Bb6bPXthQWaUjTnKPib3LGIz92JSI=; b=cq7NKAhv0KWBVB9ZThGUaZFsPflwo4Cph0TbnKL7CIcTaiYP2CypqY3Lv+MDvtqm66gl yeqjKPMzwG4fGGhSJNCRCm47G3Tu7vf+s5N8Tnj3H1bn958PpdHFSNcAjmRCgKIDCTxe osj4pBgPl+J3gSy1CHqrB46NVfpkuzZ+bT1TYZZEGjBoqkYTsdxflbGV84r6pPtJy/Op 49MsouKihA7MvRotjuR77LWnAjkT6FiF68+DDDA7KkF+tnYfqdFpMN72VhtDdTA7jQek il8L2syOzGz6q/ynAdFTWPu4i6AcXicpEVrk0yv/c8hGj+VbryANDtTI9IDL39IszggN Ig== 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 3kfagcdyby-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 28 Oct 2022 17:40:53 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id F421010003D; Fri, 28 Oct 2022 17:40:48 +0200 (CEST) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id C5A8C229A8D; Fri, 28 Oct 2022 17:40:48 +0200 (CEST) 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; Fri, 28 Oct 2022 17:40:45 +0200 Message-ID: <123f7625-98be-a5ee-40c7-f743dbc326fa@foss.st.com> Date: Fri, 28 Oct 2022 17:40:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 To: Content-Language: en-US From: Torbjorn SVENSSON Subject: Generate porting.info in build tree rather than source tree CC: Mike Frysinger Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit 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-28_07,2022-10-27_01,2022-06-22_01 X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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: Hello, With the recent improvements in the build system by Mike Frysinger, I've noticed a minor regression. When building newlib, the file libgloss/doc/porting.info is always created in the source tree rather than the build tree. Looking at the libgloss/Makefile.* files, it appears that this is derived from the libgloss/doc/Makefile.inc line: info_TEXINFOS += %D%/porting.texi To my knowledge (no automake wiz...), %D% is a relative path, so I suppose the generated path should not use $(srcdir), yet the Makefile.in does contain $(srcdir)/doc/porting.info. Would it be possible to have this porting.info file generated in the build tree rather than the source tree to avoid having the source tree in a dirty state after a build? I've spotted this building newlib for arm-none-eabi. Kind regards, Torbjörn