From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 240033858C78; Wed, 3 May 2023 20:49:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 240033858C78 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683146962; bh=8WGxVsOJRlLdXM8n/ZmgKIB0//j++h+/oB7G9dz0zIs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YozIB54NN4rsmoPtN41A6LZEP1W6OmKzXkJGv+Ak6wwggFyfr973DnZshI6rC/5Rm qRu61Lz/jZjDQbc+a6flcl1hbAFGmdCO1WOCNK2mf8h5vZGeAx8Iep4xcA2OGv55Ll NeFW7v845n3oyPQj935VrMkGvYEgEzPhN14vM5ZY= From: "redi at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: build, documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109709 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #4 from Jonathan Wakely --- 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; t= ar 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.=