From: Harry Putnam <reader@newsguy.com>
To: gcc-help@gcc.gnu.org
Subject: compile error with gcc-3.0.1
Date: Thu, 25 Oct 2001 08:50:00 -0000 [thread overview]
Message-ID: <m1adyfbu2k.fsf@reader.newsguy.com> (raw)
Setup: Redhat Linux 7.1
rpm -q gcc = gcc-2.96-85
First let me ask if the jargonized instruction at:
file:/home/reader/t/newtar/gcc-3.0.1/INSTALL/configure.html
>> First, we highly recommend that GCC be built into a separate directory
>> than the sources which does not reside within the source tree. This is
>> how we generally build GCC; building where srcdir == objdir should
>> still work, but doesn't get extensive testing; building where objdir
>> is a subdirectory of srcdir is unsupported.
Means something besides:
tar czvf gcc*3.tar.gz
cd gcc*3
./configure
make
make install
If so, that may be the source of my trouble. I followed the
proceedure above.
I'm not savvy enough about compiler errors to know what this means.
Attempting to compile gcc-3.0.1 I get an error on `make install', the tail of
which looks like:
[....]
make[1]: Leaving directory `/home/reader/t/newtar/gcc-3.0.1/libiberty'
make[1]: Entering directory `/home/reader/t/newtar/gcc-3.0.1/i586-pc-linux-gnu/l
ibstdc++-v3'
Making install in include
make[2]: Entering directory `/home/reader/t/newtar/gcc-3.0.1/i586-pc-linux-gnu/l
ibstdc++-v3/include'
sed -e '/^#/s/\([ABCDEFGHIJKLMNOPQRSTUVWXYZ_][ABCDEFGHIJKLMNOPQRSTUVWXYZ_]*\)/_G
LIBCPP_\1/g' \
-e 's,^#include "\(.*\)",#include <bits/\1>,g' \
< /home/reader/t/newtar/gcc-3.0.1/i586-pc-linux-gnu/libstdc++-v3/../gcc/gthr
.h > i586-pc-linux-gnu/bits/gthr.h
/bin/sh: /home/reader/t/newtar/gcc-3.0.1/i586-pc-linux-gnu/libstdc++-v3/../gcc/g
thr.h: No such file or directory
make[2]: *** [i586-pc-linux-gnu/bits/gthr.h] Error 1
make[2]: Leaving directory `/home/reader/t/newtar/gcc-3.0.1/i586-pc-linux-gnu/li
bstdc++-v3/include'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/reader/t/newtar/gcc-3.0.1/i586-pc-linux-gnu/li
bstdc++-v3'
make: *** [install-target-libstdc++-v3] Error 2
reply other threads:[~2001-10-25 8:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m1adyfbu2k.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
--cc=gcc-help@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).