From: David Greene <greened@eecs.umich.edu>
To: Joe Buck <jbuck@synopsys.com>
Cc: egcs@cygnus.com
Subject: Re: Template Instantiation
Date: Mon, 09 Feb 1998 11:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980209123847.2805A-100000@drakh.eecs.umich.edu> (raw)
In-Reply-To: <199802091728.JAA10214@atrus.synopsys.com>
On Mon, 9 Feb 1998, Joe Buck wrote:
> > CXXFLAGS = -DDEBUG=0 -DLINUX_LIBC6 -pipe -frtti -Wno-reorder \
> > -Wno-unused
> >
> > I get lots and lots of undefined symbols, all of them from
> > templates.
>
> I didn't state something because I assumed you knew it: the compiler
> must see the definitions of your template functions, not just their
> declarations. Definitions must be visible at the point of use. With
> or without -frepo, the compiler and linker won't go looking in other
> files for template definitions.
Ack! How did I forget that?! Duh...
Thanks for your help!
-Dave
prev parent reply other threads:[~1998-02-09 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-08 11:38 David Greene
1998-02-08 18:44 ` Joe Buck
1998-02-09 9:08 ` David Greene
1998-02-09 11:54 ` Joe Buck
1998-02-09 11:54 ` David Greene [this message]
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=Pine.LNX.3.96.980209123847.2805A-100000@drakh.eecs.umich.edu \
--to=greened@eecs.umich.edu \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.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).