From: "Orn E. Hansen" <oe.hansen@oehansen.pp.se>
To: egcs@cygnus.com
Subject: multiple definitions of....
Date: Wed, 10 Dec 1997 03:46:00 -0000 [thread overview]
Message-ID: <XFMail.971210123242.oe.hansen@oehansen.pp.se> (raw)
As was reported yesterday, the new snapshot has a problem with strings.
Now, it isn't difficult to compile bastring.cc as a template class, and
include it, but in a program I get this additional error
----
Balance.o(.data+0x20): multiple definition of `__default_alloc_template<false,
0>::free_list'
main.o(.data+0x34c): first defined here
collect2: ld returned 1 exit status
make: *** [bokhald] Error 1
----
Is there a way to neatly bypass this error, until a solution to the
above has been done (I assume one will be done?).
----------------------------------------------------------------------------
Orn Einar Hansen oe.hansen@oehansen.pp.se
oehansen@daimi.aau.dk
voice+fax; +46 035 217194
next reply other threads:[~1997-12-10 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 3:46 Orn E. Hansen [this message]
[not found] <XFMail.971210123242.oe.hansen.cygnus.egcs@oehansen.pp.se>
1997-12-10 10:58 ` Jason Merrill
1997-12-11 6:54 ` Orn E. Hansen
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=XFMail.971210123242.oe.hansen@oehansen.pp.se \
--to=oe.hansen@oehansen.pp.se \
--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).