How is the linking of executable files with loadable modules carried over?

I have a project on my hand with some libraries that are compiled as loadable modules, i.e. associated with the libtool flag -module. It is assumed that these libraries contain all the necessary functions on their own or their dependencies, that is, they should give a complete program when connected to a simple main () function, which simply calls all the functions of the module interface for my program.

Since I used to have problems with incomplete and, therefore, unusable modules, I have some simple verification programs that contain only main () and are associated with modules. When a function is missing, the linker screams with appropriate warnings, so everything is fine there. However, libtool gives me one warning:

*** Warning: Linking the executable checkplugin_locprec against the loadable module
*** liblocprec.so is not portable!

I understand the purpose and intent of this warning (do not associate the program with the library built with -module), but not its seriousness, and what is my question:

How serious is this warning? Am I just lucky that this works on the platforms that I am compiling for (i386 / x86_64 Linux and MinGW), or is this a warning relevant only for some obscure rear tree platform that I can safely ignore?

+5
1

- Mac OS X. , , . libtool, , , .

+2

All Articles