I'm in the middle of updating my quantlib package and the test suite is producing a failure that doesn't occur on any other platform. Basically are there any known issues with the lifetime of static variables with the november gcc update?
Mac OS X has always had issues with static variables in C++. Some programs depend on all static variables being init'ed on startup, but on OS X they are only init'ed when the module (.o) is actually used. This is a problem if a module's being used depends on its initializers, ie:
static int Foo::ID = Bar.registerForUse(FooFactory());
If this is the problem you're seeing, there's a fix (basically link the .o's together into one module, then link that into the lib, I think KDE still uses this fix). If it's something else, try giving more details and we'll see what can be done.
Dave
PGP.sig
Description: This is a digitally signed message part
