https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109709
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
gcc/Makefile.in has:
# Install the include directory using tar.
install-headers-tar: stmp-int-hdrs install-include-dir
# We use `pwd`/include instead of just include to problems with CDPATH
# Unless a full pathname is provided, some shells would print the new CWD,
# found in CDPATH, corrupting the output. We could just redirect the
# output of `cd', but some shells lose on redirection within `()'s
(cd `${PWD_COMMAND}`/include ; \
tar -cf - .; exit 0) | (cd $(DESTDIR)$(libsubdir)/include; tar xpf - )
(cd `${PWD_COMMAND}`/include-fixed ; \
tar -cf - .; exit 0) | (cd $(DESTDIR)$(libsubdir)/include-fixed; tar
xpf - )
# /bin/sh on some systems returns the status of the first tar,
# and that can lose with GNU tar which always writes a full block.
# So use `exit 0' to ignore its exit status.
This doesn't require GNU tar though, just any tar, so I think I agree that it's
just like cp and file and sed which are part of any unix-like environment.
The prerequisites page is specifically saying that GNU tar is needed on some
systems, for the reason Andrew stated above.
