|
|
I spoke too soon. At link time I get many many errors like
ld: multiple definitions of symbol
___tfQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl
Calendars/.libs/libCalendars.al(frankfurt.lo) definition of
___tfQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl in section
(__TEXT,__StaticInit)
Calendars/.libs/libCalendars.al(frankfurt.lo) definition of
___tfQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl in section
(__TEXT,__StaticInit)
ld: multiple definitions of symbol
___tiQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl
Calendars/.libs/libCalendars.al(frankfurt.lo) definition of
___tiQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl in section
(__DATA,__common)
Calendars/.libs/libCalendars.al(frankfurt.lo) definition of
___tiQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl in section
(__DATA,__common)
I can't quite figure out what's going on here, but libtool is magic
beyond my ken. I've tried the basics like "nm libCalendars.al | grep
___tfQ48QuantLib9Calendars9Frankfurt15FFTCalendarImpl", which only
revealed one instance of the symbol. Not surprising, since the
redundancy seems to be in the same file. Hm.
I think this is the well-known problem with the Mac OS X linker being
very picky about symbols. I'll hack a bit at it (maybe the two level
namespace thing will help), but I thought I'd mention this, just in case
anyone has any suggestions.
--Johann
|
Locked
