From: Stephen Williams <steve@icarus.icarus.com>
To: egcs@cygnus.com
Subject: g++ on alpha
Date: Wed, 18 Mar 1998 14:08:00 -0000 [thread overview]
Message-ID: <199803180308.TAA01348@icarus.icarus.com> (raw)
I seem to be having difficulty with G++ from egcs-1.0.2 for the target
alpha-redhat-linux-gnu. I'm getting messages that seem like maybe there
is a mixup of header files or something. I configured egcs-1.0.2 with
--prefix=/usr/local, and I'm using the as/ld that is installed with
RedHat 5.0/alpha. (The README doesn't seem to say I need to do otherwise.)
egch gcc compiled the 2.1.89 kernel great, that is what I'm running.
C++ is another story. Did I do something stupid?
--
Steve Williams "The woods are lovely, dark and deep.
steve@icarus.com But I have promises to keep,
steve@picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
icarus.icarus.com % make
g++ -O -g -Wall -MD -c pform.cc -o pform.o
/usr/local/include/g++/stl_list.h: In method `void Module::add_gate(class Gate *)':
/usr/local/include/g++/stl_list.h:159: warning: `struct cp_eh_info * __exception_info' might be used uninitialized in this function
/usr/local/include/g++/stl_list.h: In method `void Module::add_wire(class Wire *)':
/usr/local/include/g++/stl_list.h:159: warning: `struct cp_eh_info * __exception_info' might be used uninitialized in this function
/usr/local/include/g++/stl_list.h: In function `void pform_startmodule(const class basic_string<char,string_char_traits<char>,__default_alloc_template<true,0> > &)':
/usr/local/include/g++/stl_list.h:159: warning: `struct cp_eh_info * __exception_info' might be used uninitialized in this function
/tmp/cca01289.s: Assembler messages:
/tmp/cca01289.s:6341: Fatal error: String too big (4145 bytes)
make: *** [dep/pform.d] Error 1
reply other threads:[~1998-03-18 14:08 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=199803180308.TAA01348@icarus.icarus.com \
--to=steve@icarus.icarus.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).