Re: g++ 3.4.4: all global constructors in archive not called

Lewis Hyatt wrote: Patric Ljung itn.liu.se> writes: I have just ported an application from Linux to Cygwin. In one archive (.a) I have several global constructors, 2-3 in two .o files. When I run my program only one initializer function is called in that archive. Leaving the other uninitialize

Re: g++ 3.4.4: all global constructors in archive not called

Patric Ljung itn.liu.se> writes: > > Dear cygwin readers, > > I have just ported an application from Linux to Cygwin. > In one archive (.a) I have several global constructors, > 2-3 in two .o files. When I run my program only one > initializer function is called in that archive. Leaving > the

g++ 3.4.4: all global constructors in archive not called

Dear cygwin readers, I have just ported an application from Linux to Cygwin. In one archive (.a) I have several global constructors, 2-3 in two .o files. When I run my program only one initializer function is called in that archive. Leaving the other uninitialized/uncalled. I have found this is