public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dave madden <dhm@paradigm.webvision.com>
To: gregg@eoeml.gtri.gatech.edu
Cc: egcs@cygnus.com
Subject: Re: C++ and DEC Unix: string too long
Date: Tue, 28 Oct 1997 17:57:00 -0000	[thread overview]
Message-ID: <199710290024.QAA05079@paradigm.webvision.com> (raw)
In-Reply-To: <199710282025.PAA07209@nospokes.gtri.gatech.edu>

 =>From: Greg Galloway <gregg@eoeml.gtri.gatech.edu>
 =>...
 =>Has anyone got EGCS/C++ to work on an Alpha under DEC Unix 3.2?
 =>I get an error about string too long because the mangled name of
 =>a template instantiation (hash_map in this case) is 4144 chars
 =>long.

I've gotten the same message under DEC Unix 4.0; you can get around it
by not compiling with debugging information (-g).  (Of course, this
means you can't debug, but that's the way it goes.)  I don't know any
other workaround, but would be glad to hear of one...

d.

  reply	other threads:[~1997-10-28 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-28 12:21 Greg Galloway
1997-10-28 17:57 ` dave madden [this message]
1997-10-28 15:21 Corey Kosak
1997-10-28 19:48 ` Joe Buck

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=199710290024.QAA05079@paradigm.webvision.com \
    --to=dhm@paradigm.webvision.com \
    --cc=egcs@cygnus.com \
    --cc=gregg@eoeml.gtri.gatech.edu \
    /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).