public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neroden at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/11932] [3.4 regression] Parallel bootstrap failure with sparc libiberty multilib
Date: Sat, 03 Jan 2004 21:40:00 -0000 [thread overview]
Message-ID: <20040103214054.16482.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030815185146.11932.lucier@math.purdue.edu>
------- Additional Comments From neroden at gcc dot gnu dot org 2004-01-03 21:40 -------
OK, I found time to actually analyze this. Looking at the original bug report
here, there's something very funny going on.
Checking multilib configuration...
/local/bin/bash ../mkinstalldirs sparc-sun-solaris2.8/libstdc++-v3 ; \
rm -f sparc-sun-solaris2.8/libstdc++-v3/Makefile || : ; \
cp multilib.out sparc-sun-solaris2.8/libstdc++-v3/multilib.out
/local/bin/bash ../mkinstalldirs sparc-sun-solaris2.8/libiberty ; \
rm -f sparc-sun-solaris2.8/libiberty/Makefile || : ; \
cp multilib.out sparc-sun-solaris2.8/libiberty/multilib.out
/local/bin/bash ../mkinstalldirs sparc-sun-solaris2.8/libf2c ; \
rm -f sparc-sun-solaris2.8/libf2c/Makefile || : ; \
cp multilib.out sparc-sun-solaris2.8/libf2c/multilib.out
^^^^
This stuff is the top-level work copying multilib.out, and it's correct.
mkdir -p -- sparc-sun-solaris2.8/libstdc++-v3
mkdir -p -- sparc-sun-solaris2.8/libiberty
mkdir -p -- sparc-sun-solaris2.8/libf2c
^^^^
These messages look like they're coming from mkinstalldirs, which is running
mkdir -p.
mkdir: No such file or directory
mkdir: Failed to make directory "sparc-sun-solaris2.8/libiberty"; File exists
^^^^
What the heck is up with these? Obviously the mkdir -p invocations are
failing. Can you point me to the Solaris 8 manpage for mkdir?
cp: cannot create sparc-sun-solaris2.8/libiberty/multilib.out: No such file or
directory
^^^^
This is because sparc-sun-solaris2.8/libiberty didn't get created by 'mkdir
-p'.
make[1]: *** [sparc-sun-solaris2.8/libiberty/multilib.out] Error 2
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11932
next prev parent reply other threads:[~2004-01-03 21:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 18:51 [Bug bootstrap/11932] New: " lucier at math dot purdue dot edu
2003-08-15 19:06 ` [Bug bootstrap/11932] " pinskia at gcc dot gnu dot org
2003-08-23 1:18 ` [Bug bootstrap/11932] [3.4 regression] " dhazeghi at yahoo dot com
2003-08-24 21:52 ` dhazeghi at yahoo dot com
2003-08-25 4:31 ` pinskia at gcc dot gnu dot org
2003-08-27 21:47 ` neroden at gcc dot gnu dot org
2003-12-16 22:42 ` steven at gcc dot gnu dot org
2003-12-19 10:15 ` pinskia at gcc dot gnu dot org
2003-12-31 21:51 ` neroden at gcc dot gnu dot org
2003-12-31 21:56 ` lucier at math dot purdue dot edu
2004-01-03 18:23 ` cvs-commit at gcc dot gnu dot org
2004-01-03 21:40 ` neroden at gcc dot gnu dot org [this message]
2004-01-03 21:43 ` neroden at gcc dot gnu dot org
2004-01-05 6:11 ` neroden at gcc dot gnu dot org
2004-01-06 4:52 ` pinskia at gcc dot gnu dot org
2004-01-06 5:21 ` lucier at math dot purdue dot edu
2004-01-06 23:32 ` neroden at gcc dot gnu dot org
2004-01-09 1:44 ` neroden at gcc dot gnu dot org
2004-01-13 3:19 ` lucier at math dot purdue dot edu
2004-01-13 23:13 ` neroden at gcc dot gnu dot org
2004-01-14 0:58 ` lucier at math dot purdue dot edu
2004-01-14 5:57 ` neroden at twcny dot rr dot com
2004-01-27 6:03 ` [Bug bootstrap/11932] [3.4/3.5 " neroden at gcc dot gnu dot org
2004-01-27 6:22 ` Ian Lance Taylor
2004-01-27 6:22 ` ian at wasabisystems dot com
2004-02-04 17:04 ` ghazi at gcc dot gnu dot org
2004-02-05 0:27 ` neroden at twcny dot rr dot com
2004-02-05 2:21 ` ghazi at caip dot rutgers dot edu
2004-02-20 2:01 ` cvs-commit at gcc dot gnu dot org
2004-02-20 2:05 ` neroden at gcc dot gnu dot org
2004-02-20 2:12 ` lucier at math dot purdue dot edu
2004-02-20 2:13 ` [Bug bootstrap/11932] [3.4 " pinskia at gcc dot gnu dot org
2004-02-25 23:31 ` neroden at gcc dot gnu dot org
2004-02-25 23:46 ` cvs-commit 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=20040103214054.16482.qmail@sources.redhat.com \
--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).