public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* gcc v3.4.3 related question
@ 2004-12-08 19:38 Jeffrey Holle
  0 siblings, 0 replies; only message in thread
From: Jeffrey Holle @ 2004-12-08 19:38 UTC (permalink / raw)
  To: gcc-help

I'm asking this question with the hope that my confidence will be 
strengthened that a future build option will solve my problem.

I am attempting to use boost.serialization library on a rather large 
shared library whose data needs to be persisted.

Presently, with the Boost v1.32.0 release, this library is only 
available as a static library (*.a).

I can successfully build and use my shared library when I have only a 
few serialize methods implemented.

However, when I add the rest (34), I get link errors associated with the 
booost.serialization library.

This doesn't appear to be related to a particular module.  Instead it 
starts happening when about 14 serialize methods are added.

It should be noted that boost.serialization makes extreme use of templates.

Work is presently being done to make this library available as shared 
library.

My questions are:

1.  Is there an explaination for this problem?
2.  Will using a shared library instead of a static one likely help?
3.  Should I perhaps try older versions of gcc? (presently I'm using v3.4.3)

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-12-08 19:38 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-08 19:38 gcc v3.4.3 related question Jeffrey Holle

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).