public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cross+gcc at distal dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/15379] 'make install' fails Date: Wed, 12 May 2004 19:36:00 -0000 [thread overview] Message-ID: <20040512063406.21243.qmail@sourceware.org> (raw) In-Reply-To: <20040511172605.15379.andreas@florath.net> ------- Additional Comments From cross+gcc at distal dot com 2004-05-12 06:34 ------- Okay. I just set CONFIG_SHELL (exported), then reran configure, then gmake bootstrap, then gmake install. Same failure: rm -f /usr/local/bin/g++ ../gcc-3.4.0/install-sh -c g++ /usr/local/bin/g++ /bin/ksh: ../gcc-3.4.0/install-sh: not found gmake[1]: [c++.install-common] Error 127 (ignored) That's being passed into gcc/Makefile as INSTALL (or INSTALL_SCRIPT). I'm not sure how to fix this, but it's definately still a bug in the build process... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15379
prev parent reply other threads:[~2004-05-12 6:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-12 13:42 [Bug bootstrap/15379] New: " andreas at florath dot net 2004-05-12 13:49 ` [Bug bootstrap/15379] " pinskia at gcc dot gnu dot org 2004-05-12 19:31 ` cross+gcc at distal dot com 2004-05-12 19:36 ` cross+gcc at distal dot com [this message]
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=20040512063406.21243.qmail@sourceware.org \ --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: linkBe 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).