From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 5D51F3858418 for ; Sat, 29 Oct 2022 14:46:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5D51F3858418 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gentoo.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gentoo.org Received: by smtp.gentoo.org (Postfix, from userid 559) id ECFF1340C3C; Sat, 29 Oct 2022 14:46:48 +0000 (UTC) Date: Sat, 29 Oct 2022 19:17:26 +0545 From: Mike Frysinger To: Torbjorn SVENSSON Cc: newlib@sourceware.org Subject: Re: Generate porting.info in build tree rather than source tree Message-ID: Mail-Followup-To: Torbjorn SVENSSON , newlib@sourceware.org References: <123f7625-98be-a5ee-40c7-f743dbc326fa@foss.st.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qkpQX/sDaiG5pQGc" Content-Disposition: inline In-Reply-To: <123f7625-98be-a5ee-40c7-f743dbc326fa@foss.st.com> X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,KAM_SHORT,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --qkpQX/sDaiG5pQGc Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 28 Oct 2022 17:40, Torbjorn SVENSSON wrote: > With the recent improvements in the build system by Mike Frysinger, I've= =20 > noticed a minor regression. this is not new behavior. you can check out newlib-4.1.0 which doesn't contain any of my build changes and it does the same thing. > When building newlib, the file libgloss/doc/porting.info is always=20 > created in the source tree rather than the build tree. Looking at the=20 > libgloss/Makefile.* files, it appears that this is derived from the=20 > libgloss/doc/Makefile.inc line: > info_TEXINFOS +=3D %D%/porting.texi >=20 > To my knowledge (no automake wiz...), %D% is a relative path, so I=20 > suppose the generated path should not use $(srcdir), yet the Makefile.in= =20 > does contain $(srcdir)/doc/porting.info. >=20 > Would it be possible to have this porting.info file generated in the=20 > build tree rather than the source tree to avoid having the source tree=20 > in a dirty state after a build? this is WAI. info files are distributed with releases, so it should be generated in the source tree. this is documented here: https://www.gnu.org/prep/standards/html_node/Standard-Targets.html#Standard= -Targets > 'info' > Normally a GNU distribution comes with Info files, and that means the Info > files are present in the source directory. Therefore, the Make rule for an > info file should update it in the source directory. When users build the > package, ordinarily Make will not update the Info files because they will > already be up to date. -mike --qkpQX/sDaiG5pQGc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmNdK2oACgkQQWM7n+g3 9YEOtg/+KCg5iWX54nQoSIh8Wq0r+TO95vyhtPp4mlUvqW070rOt9WnjkuuojTK5 sx6XuDqWxkwiaB75dKp6WMPS8jPR5029FLPqo1Jp6prVc8PDmVxcEm02WLWaV34k oGO37Xfge2DShXCocHnFlCHP6dGKCkYgFCdIYMfQtUtLiFHK/S0inGdeHG+9t715 XTIvlizeus8/QIdX00ETGYO131i/3V+IOGQfnpEDpqRHjLGx6v1XrpNBcU00/XDa cJU/ZUjXXzk6P7reIVydNsWwQwEwZ1vnw6FkH/4lxVZXQYZ+NU1c509KrGkCD3fA 0msDp8oiVb0z4fVTt7H+i/A0eXqNoIEF9vIFOv9mL8dq+IbWrsmnZ6gNoK4+Wbcl DF5sLimFKXqpU/XG44lPMoJiCaLwXSUDxeTGeNFuxtUzsahBweIXUBwIt8u+qbdA XYEgxidgEXqHTG90rRQUQN9J2RygGYVK+I4JXZ4xAjfxiKGaEGxqMScVi0Dm0P1F YIHlFNBOUiyQTCb3Kmm4CrdZiKXO7t9Nu+w5SIWEwti1bg+SFwS5TNfKaXBvQdOQ dhxXbgLMduRuilhN9HoBgbMmvy+hl6Czxb81Wkzvv1k5FfcqoQHQuFfwM5QB4FTt hHLZLJ4STEfI3eqmfuocGGYz7J1bw/MN6lAi3tk5wnd2kZwzg9c= =VooA -----END PGP SIGNATURE----- --qkpQX/sDaiG5pQGc--