public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/42980] GCC parallel "make install" failures
Date: Mon, 07 Nov 2011 15:08:00 -0000 [thread overview]
Message-ID: <bug-42980-4-YLcMTTRUEO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42980-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42980
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jb at gcc dot gnu.org
--- Comment #17 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-11-07 15:07:09 UTC ---
I now get this when bootstrapping today's trunk and then "make -j4 install":
/usr/bin/install: cannot create regular file
`/home/janne/src/gfortran/trunk/install/bin/gcc-ar': No such file or directory
make[2]: *** [install-gcc-ar] Error 1
As a result, my install/bin directory is empty. Running "make install" fixes
the problem, suggesting a race somewhere. Perhaps due to Rainer's recent move
of configury logic to libgcc?
My configure line:
nice ../$SRCDIR/configure --enable-checking \
--prefix=/home/janne/src/gfortran/$GCCDIR/install
--enable-languages=fortran \
--enable-maintainer-mode \
--enable-__cxa_atexit \
--disable-bootstrap \
--enable-threads=posix \
--disable-multilib
Target & host: x86_64-unknown-linux-gnu
next prev parent reply other threads:[~2011-11-07 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42980-4@http.gcc.gnu.org/bugzilla/>
2011-06-20 16:34 ` hp at gcc dot gnu.org
2011-06-22 21:35 ` rwild at gcc dot gnu.org
2011-06-22 22:19 ` gary at intrepid dot com
2011-11-07 15:08 ` jb at gcc dot gnu.org [this message]
2010-02-05 21:46 [Bug other/42980] New: GCC parllel " gary at intrepid dot com
2010-02-08 18:18 ` [Bug other/42980] GCC parallel " rwild at gcc dot gnu dot org
2010-02-08 23:11 ` gary at intrepid dot com
2010-02-21 16:13 ` rwild at gcc dot gnu dot org
2010-02-22 17:48 ` gary at intrepid dot com
2010-02-24 22:15 ` rwild at gcc dot gnu dot org
2010-02-24 22:17 ` rwild at gcc dot gnu dot org
2010-02-24 22:18 ` rwild at gcc dot gnu dot org
2010-02-24 22:22 ` rwild at gcc dot gnu dot org
2010-02-28 9:57 ` rwild at gcc dot gnu dot org
2010-02-28 10:41 ` pluto at agmk dot net
2010-03-02 6:10 ` rwild at gcc dot gnu dot org
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-42980-4-YLcMTTRUEO@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).