From: Godmar Back (gback@cs.utah.edu)
Date: Tue Jan 26 1999 - 11:23:44 EST
Alexandre,
I first thought that the error message I sent was just because
I had made changes, but it now shows up all the time:
*** Warning: libtool could not satisfy all dependencies of module libnative
*** Therefore, instead of creating a dynamic module that would not run,
*** libtool will create a static module. As long as the dlopening
*** application is linked with the -dlopen flag, this should be enough.
At first, it went unnoticed because the amount of characters produced
by a build these days far outstrips what fits in my scrollback buffer.
Is this something we need to be concerned about?
How do I find out what the unsatisfied dependencies are?
Also, is libtool talking about its fancy notion of interlibrary
dependencies or is this plain symbol dependencies that would normally
lead to unresolved symbol errors?
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:48 EDT