From: Mike Gruber <grubinski@seanet.com>
To: crossgcc@cygnus.com, egcs@cygnus.com
Subject: Cross compiler with egcs, using GNAT, question
Date: Tue, 07 Jul 1998 09:25:00 -0000 [thread overview]
Message-ID: <35A23284.ED2C8EDF@seanet.com> (raw)
Hi:
Has anybody done a cross compiler based on egcs and including the gnat
ada front end? I got most of it, but it doesn't want to compile
gnatlib. I'm curious if this is a cross compiler problem only, or if
it's some known bug that I haven't read about. Here's the last bit of
the build, showing the error message...
make[1]: `../../../gcc/ada/a-cstrea.o' is up to date.
make[1]: `a-errno.o' is up to date.
make[1]: `../../../gcc/ada/a-exit.o' is up to date.
make[1]: `../../../gcc/ada/a-raise.o' is up to date.
make[1]: `../../../gcc/ada/a-sysdep.o' is up to date.
make[1]: `a-time.o' is up to date.
make[1]: `io-aux.o' is up to date.
make[1]: `../../../gcc/ada/a-init.o' is up to date.
make[1]: `../../../gcc/ada/a-final.o' is up to date.
make[1]: `../../../gcc/ada/ada.o' is up to date.
../../xgcc -B../../ -c -O2 -I/usr/local/m68k-headers -UIN_GCC -gnatpg
-I. -I../../../gcc/ada calendar.ads
xgcc: Internal compiler error: program gnat1 got fatal signal 11
make[1]: *** [calendar.o] Error 1
make[1]: Leaving directory
`/home/Mike/Programming/egcs-19980628/objdir/gcc/ada/rts'
make: *** [gnatlib-common] Error 2
Shadowfax:/home/Mike/Programming/egcs-19980628/objdir/gcc/ada# exit
exit
I looked at calendar.ads, and it seems fine.
Any hints appreciated, thanks!
Mike Gruber
next reply other threads:[~1998-07-07 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-07 9:25 Mike Gruber [this message]
1998-07-08 0:24 ` Jeffrey A Law
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=35A23284.ED2C8EDF@seanet.com \
--to=grubinski@seanet.com \
--cc=crossgcc@cygnus.com \
--cc=egcs@cygnus.com \
/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).