public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/109709] List of prerequisites should include that tar is required (not only for unpacking the source).
Date: Wed, 03 May 2023 20:49:21 +0000	[thread overview]
Message-ID: <bug-109709-4-LEsyDU3tSU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109709-4@http.gcc.gnu.org/bugzilla/>

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.

  parent reply	other threads:[~2023-05-03 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 10:19 [Bug other/109709] New: " me at manueljacob dot de
2023-05-03 10:25 ` [Bug other/109709] " rguenth at gcc dot gnu.org
2023-05-03 12:45 ` pinskia at gcc dot gnu.org
2023-05-03 20:42 ` [Bug bootstrap/109709] " me at manueljacob dot de
2023-05-03 20:49 ` redi at gcc dot gnu.org [this message]
2023-05-03 20:51 ` redi at gcc dot gnu.org
2023-05-04  2:24 ` sjames at gcc dot gnu.org
2023-05-04 12:34 ` redi at gcc dot gnu.org
2023-05-04 12:42 ` me at manueljacob dot de

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109709-4-LEsyDU3tSU@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).