On 13/05/13 14:46, David Aldrich wrote: > (...) > Attempting to load file libD > Failed to load libD > Attempting to load file libE > Failed to load libE > > PASS 2 > Attempting to load file libB > Loading libB > Attempting to load file libD > < dlopen( ..., RTLD_NOLOAD) returns a handle - i.e. it thinks library D is already loaded, so we don't try to load it > Attempting to load file libE Loading libC > > So the code thinks that all the libraries loaded, but actually libD never got loaded. On the first pass LibD failed to load, but on the second pass the code believes the libD is already loaded and doesn't try to load it again. > > It is odd that this changed behaviour is associated with moving from gcc 4.1 to gcc 4.4. > > Please can anyone suggest a fix for this problem? > > Best regards > > David Is it possible that when loading libB, libD got loaded as a dependency?
