From: Mike Stump <mrs@windriver.com>
To: PushpamX.Rajah@dialogic.com, gcc@gcc.gnu.org
Subject: Re: problem while compiling Binutils On Solaris
Date: Thu, 26 Apr 2001 15:59:00 -0000 [thread overview]
Message-ID: <200104262259.PAA08102@kankakee.wrs.com> (raw)
I think you have us confused with the binutils people, we are not
them, the below appears to be a problem in GNU as. I'd recommend
reading the GNU as documentation on reporting bugs.
> From: "Rajah, PushpamX" <PushpamX.Rajah@dialogic.com>
> To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
> Date: Thu, 26 Apr 2001 16:12:31 -0400
> > I tried compiling in binutils for Sparc Solaris 2.6. I didn't give any
> > option in configure. while compiling it give me the below error
> >
> > gcc -DHAVE_CONFIG_H -I. -I../../binutils-2.10.1/bfd -I. -D_GNU_SOURCE -I.
> > -I../.
> > ./binutils-2.10.1/bfd -I../../binutils-2.10.1/bfd/../include
> > -I../../binutils-2.
> > 10.1/bfd/../intl -I../intl -g -O2 -W -Wall -c
> > ../../binutils-2.10.1/bfd/coff-stg
> > o32.c -o coff-stgo32.o
> > gcc: Internal compiler error: program as got fatal signal 10
> > make[3]: *** [coff-stgo32.lo] Error 1
> > make[3]: Leaving directory `/export/home/pushpa/BinUtils/bfd'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/export/home/pushpa/BinUtils/bfd'
> > make[1]: *** [all-recursive-am] Error 2
> > make[1]: Leaving directory `/export/home/pushpa/BinUtils/bfd'
> > make: *** [all-bfd] Error 2
> >
> > Do I need to give any other option while configure?
> >
> > Can anyone help me in that.
> >
> > Pushpa
next reply other threads:[~2001-04-26 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 15:59 Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-26 13:12 Rajah, PushpamX
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=200104262259.PAA08102@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=PushpamX.Rajah@dialogic.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).