public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yuchape at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/47859] New: Makefile: Input/output error. Stop
Date: Wed, 23 Feb 2011 14:21:00 -0000 [thread overview]
Message-ID: <bug-47859-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47859
Summary: Makefile: Input/output error. Stop
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: yuchape@gmail.com
Created attachment 23442
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23442
Makefile in .../libstdc++-v3/libsupc++/
This is the problem I encountered in the "make" stage of gcc installation.
My system is x86_64-redhat-linux (Red Hat Linux 3.2.3-56).
The configure command is "--prefix=/usr/local/gcc-4.5.2
--enable-threads=posix --disable-checking --disable-multilib
--enable-languages=c,c++,fortran --with-gmp=/usr/local/gmp-5.0.1
--with-mpfr=/usr/local/mpfr-2.4.2 --with-mpc=/usr/local/mpc-0.8.1"
make[4]: warning: Clock skew detected. Your build may be incomplete.
make[4]: Leaving directory
`/data/yuchape/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/include'
Making all in libsupc++
make[4]: Entering directory
`/data/yuchape/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++'
make[4]: *** Makefile: Input/output error. Stop.
make[4]: Leaving directory
`/data/yuchape/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/data/yuchape/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/data/yuchape/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3'
make[1]: *** [all-target-libstdc++-v3] Error 2
make[1]: Leaving directory `/data/yuchape/gcc-build'
make: *** [all] Error 2
The attachment is the Makefile in .../libstdc++-v3/libsupc++/
next reply other threads:[~2011-02-23 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 14:21 yuchape at gmail dot com [this message]
2011-02-23 14:28 ` [Bug libstdc++/47859] " redi at gcc dot gnu.org
2011-02-23 14:29 ` redi at gcc dot gnu.org
2011-02-23 14:31 ` yuchape at gmail dot com
2011-02-23 14:41 ` yuchape at gmail dot com
2011-02-23 15:00 ` redi at gcc dot gnu.org
2011-02-23 21:37 ` pinskia at gcc dot gnu.org
2011-03-29 16:52 ` redi at gcc dot gnu.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-47859-4@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).