public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/19364] New: embedded sparc does not bootstrap
Date: Mon, 10 Jan 2005 15:15:00 -0000 [thread overview]
Message-ID: <20050110151452.19364.joel@gcc.gnu.org> (raw)
The embedded SPARC targets have developed a dependency on a Solaris specific
file. This is a regression from the 3.3 and 3.4 series.
gcc -c -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -fno-common
-DHAVE_CONFIG_H -I. -I. -I../../gcc-4.0.20050109/gcc
-I../../gcc-4.0.20050109/gcc/. -I../../gcc-4.0.20050109/gcc/../include
-I../../gcc-4.0.20050109/gcc/../libcpp/include \
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c -o sparc.o
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error:
`solaris_insert_attributes' undeclared here (not in a function)
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error: initializer element
is not constant
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error: (near initialization
for `targetm.insert_attributes')
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error: initializer element
is not constant
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error: (near initialization
for `targetm.calls')
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error: initializer element
is not constant
../../gcc-4.0.20050109/gcc/config/sparc/sparc.c:504: error: (near initialization
for `targetm.cxx')
make[1]: *** [sparc.o] Error 1
make[1]: Leaving directory
`/home/rtems/src/packages/SOURCES/b-gcc/b-gccsparccelf/gcc'
make: *** [all-gcc] Error 2
--
Summary: embedded sparc does not bootstrap
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: joel at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: sparc-unknown-elf sparc-unknown-rtems*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19364
next reply other threads:[~2005-01-10 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 15:15 joel at gcc dot gnu dot org [this message]
2005-01-10 15:20 ` [Bug bootstrap/19364] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-10 15:32 ` ebotcazou at gcc dot gnu dot org
2005-01-10 16:29 ` joel at gcc dot gnu dot org
2005-01-10 16:54 ` ebotcazou at gcc dot gnu dot org
2005-01-10 22:33 ` joel at gcc dot gnu dot org
2005-01-10 23:01 ` ebotcazou at gcc dot gnu dot org
2005-01-11 10:35 ` jakub at gcc dot gnu dot org
2005-01-12 0:03 ` joel at gcc dot gnu dot org
2005-01-20 9:52 ` ebotcazou at gcc dot gnu dot org
2005-01-20 9:56 ` ebotcazou at gcc dot gnu dot org
2005-01-20 12:42 ` joel at gcc dot gnu dot org
2005-01-20 13:34 ` corsepiu at gcc dot gnu dot org
2005-01-20 14:18 ` joel at gcc dot gnu dot org
2005-01-20 15:24 ` ebotcazou at gcc dot gnu dot org
2005-01-20 15:32 ` ebotcazou at gcc dot gnu dot org
2005-01-20 16:12 ` corsepiu at gcc dot gnu dot org
2005-01-24 0:20 ` pinskia at gcc dot gnu dot org
2005-01-24 21:32 ` cvs-commit at gcc dot gnu dot org
2005-01-24 21:35 ` ebotcazou at gcc dot gnu dot org
2005-01-24 21:40 ` pinskia 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=20050110151452.19364.joel@gcc.gnu.org \
--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).