public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "me at manueljacob dot de" <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:42:55 +0000 [thread overview]
Message-ID: <bug-109709-4-K9D5opFALw@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
--- Comment #3 from Manuel Jacob <me at manueljacob dot de> ---
(In reply to Richard Biener from comment #1)
> Huh, can you post how it fails?
if [ -d ../prev-gcc ]; then \
cd ../prev-gcc && \
make real-install-headers-tar DESTDIR=`pwd`/../gcc/ \
libsubdir=. ; \
else \
set -e; for ml in `cat fixinc_list`; do \
sysroot_headers_suffix=`echo ${ml} | sed -e 's/;.*$//'`; \
multi_dir=`echo ${ml} | sed -e 's/^[^;]*;//'`; \
fix_dir=include-fixed${multi_dir}; \
if ! false && test ! -d `echo /usr/include | sed -e :a -e
's,[^/]*/\.\.\/,,' -e ta`; then \
echo The directory that should contain system headers does not exist: >&2
; \
echo " `echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" >&2
; \
tooldir_sysinc=`echo
"/usr/lib/gcc/x86_64-pc-linux-gnu/13.1.0/../../../../x86_64-pc-linux-gnu/sys-include"
| sed -e :a -e "s,[^/]*/\.\.\/,," -e ta`; \
if test "x`echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" =
"x${tooldir_sysinc}"; \
then sleep 1; else exit 1; fi; \
fi; \
/bin/sh /build/source/gcc-13.1.0/gcc/../mkinstalldirs ${fix_dir}; \
chmod a+rx ${fix_dir} || true; \
(TARGET_MACHINE='x86_64-pc-linux-gnu'; srcdir=`cd
/build/source/gcc-13.1.0/gcc; ${PWDCMD-pwd}`; \
SHELL='/bin/sh'; MACRO_LIST=`${PWDCMD-pwd}`/macro_list ; \
gcc_dir=`${PWDCMD-pwd}` ; \
export TARGET_MACHINE srcdir SHELL MACRO_LIST && \
cd ../build-x86_64-pc-linux-gnu/fixincludes && \
/bin/sh ./fixinc.sh "${gcc_dir}/${fix_dir}" \
`echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta` ); \
done; \
fi
make[4]: Entering directory '/build/build/prev-gcc'
(cd `${PWDCMD-pwd}`/include-fixed ; \
tar -cf - .; exit 0) | (cd /build/build/prev-gcc/../gcc/./include-fixed; tar
xpf - )
/bin/sh: line 2: tar: command not found
/bin/sh: line 2: tar: command not found
make[4]: *** [Makefile:4028: real-install-headers-tar] Error 127
make[4]: Leaving directory '/build/build/prev-gcc'
make[3]: *** [Makefile:3309: stmp-fixinc] Error 2
make[3]: Leaving directory '/build/build/gcc'
make[2]: *** [Makefile:5013: all-stage2-gcc] Error 2
make[2]: Leaving directory '/build/build'
make[1]: *** [Makefile:27012: stage2-bubble] Error 2
make[1]: Leaving directory '/build/build'
make: *** [Makefile:1080: all] Error 2
next prev parent reply other threads:[~2023-05-03 20:42 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 ` me at manueljacob dot de [this message]
2023-05-03 20:49 ` [Bug bootstrap/109709] " redi at gcc dot gnu.org
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-K9D5opFALw@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).