Re: Generate porting.info in build tree rather than source tree

On 31 Oct 2022 16:10, Torbjorn SVENSSON wrote:
> 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?

the GNU project provides no such target/config.  you can prob cheat by
setting MAKEINFO to a stub program.  or just build the info pages.  i
don't see why building them is a problem in the first place.
-mike

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmNkXP8ACgkQQWM7n+g3
9YGBGg/+IU0mavZBbuE2Zw7on3KhnUR25ChXgd/+gsSEzo/SNBFfHwvCCXRrfCoN
fJ0CXabza3oNghQhwpCfbTRvo6pj4DOlSfBr0OLoUwkMSQwjri5dK3bXkGnsyoa9
kQuw0J/4zbnnaqRmAL8/jIeEmxGbVWfkEN0Elz3CSl7tJnNS2Df3HbOszggLVRKM
uk62xRBi4EX1KW9feJpKbiOTtCw406lm4KclR/JQzY/dPNGml4EIMzkvvLdOJ9D7
3GYPbUiOp9YlCr3X4rGwWWEXUDS6JA3ANpzpUGJRF7dRt13r2tw4+itPROOiowi4
klqXJv8MUWA4iF0RGsbpFiJDiT3aoitcaKD1LR7fQ/RaRbA2nArhLmMz/cnG22g1
RK6yLERld8WL4qNpufg6dFKA5stpkKdZPORxX50Dt2oBARE9ciefQwRcykX9cdBy
UjeDY6+NRrVPoJiRfQ5AvcY+2IcdMIFkpc+Hq4jWj6RMWyuWP7jgytZgR9RSo3WF
JkUi1o0TPuxnv9Cm5lCTurFngTskNmejK+Ew8Rb4cmuawGu/ZTihOeKNvgf2f6ET
VHE+n13xWLqsbziMOzalcCATV0y46mY16H3bxZZb1PETJh0kz9adqZrGBcr7yv1h
yiyxGRCmOBY9u+gqEbcLVCOTh5Ltso+cthiPvr7FAygth/tcpX0=
=aPSB
-----END PGP SIGNATURE-----