From: Allen Wayne Best <gcc@atoka-software.com>
To: gcc@gcc.gnu.org
Subject: build of gcc 3.0.1 problems
Date: Mon, 24 Sep 2001 23:13:00 -0000 [thread overview]
Message-ID: <01092423123608.26781@jackfork.atoka.org> (raw)
hello:
i am having problems building gcc 3.0.1.
following the instructions to build in a parallel directory (universe?), i
get the following errors on make!
gcc: unrecognized option `-DIN_GCC'
gcc: unrecognized option `-DHAVE_CONFIG_H'
In file included from insn-codes.h:426,
from config.h:13,
from ../../gcc-3.0/gcc/cppspec.c:21:
../../gcc-3.0/gcc/machmode.h:124: parse error before `PARAMS'
../../gcc-3.0/gcc/machmode.h:130: parse error before `PARAMS'
../../gcc-3.0/gcc/machmode.h:136: parse error before `PARAMS'
../../gcc-3.0/gcc/machmode.h:140: parse error before `PARAMS'
../../gcc-3.0/gcc/machmode.h:145: parse error before `PARAMS'
In file included from config.h:13,
from ../../gcc-3.0/gcc/cppspec.c:21:
insn-codes.h:428: parse error before `PARAMS'
insn-codes.h:429: parse error before `PARAMS'
........
my system is linux 2.4.9 with
gcc 2.96,
make 3.79.1
m4 1.4
automake 1.5
autoconf 2.52
i did the following
tar xvzf gcc-3.0.1.tar.gz
mkdir gcc-build
cd gcc-build
../gcc-3.0.1/configure --prefix=/usr
make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 \
-fno-implicit-templates' bootstrap
any suggestions are appreciated.
--
regards,
allen wayne best, esq
"your friendly neighborhood rambler owner"
"my rambler will go from 0 to 105"
Current date: 14:2:20::266:2001
RAM wasn't built in a day.
reply other threads:[~2001-09-24 23:13 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=01092423123608.26781@jackfork.atoka.org \
--to=gcc@atoka-software.com \
--cc=gcc@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).