On Thu, Apr 13, 2006 at 02:20:35PM +0900, TAKAHASHI Tamotsu wrote: > * Tue Apr 11 2006 Ash Williams <[EMAIL PROTECTED]> > > > And libtool-linker warns that its dynamically-linking > > > capability may be disabled because several static libraries > > > are linked (e.g. libiconv.a, libintl.a, and libgcc.a). > > > I'm afraid this warning is not a false positive. > > > SCIM-SKK doesn't work with it (or am I missing anything?). > > > > Can you give this a try and tell me if you're still getting these > > libtool warning msgs - I can't seem to find what you're talking about. > > Can you paste the whole message please? > > Okay, here is the specific warning (though it shouldn't be a problem): > > === > /usr/local/bin/libtool --tag=CXX --mode=link c++ -O2 -pipe -o > libscim-1.0.la -rpath /usr/local/lib -version-info 9:0:1 -export-dynamic > -rpath /usr/local/lib /usr/local/lib/libiconv.a -L/usr/local/lib -lintl > -L/usr/local/lib -liconv -lstdc++ scim_backend.lo scim_chartraits.lo > scim_compose_key.lo scim_config_base.lo scim_config_module.lo > scim_connection.lo scim_debug.lo scim_event.lo scim_filter.lo > scim_filter_module.lo scim_filter_manager.lo scim_frontend.lo > scim_frontend_module.lo scim_global_config.lo scim_helper.lo > scim_helper_manager.lo scim_helper_module.lo scim_hotkey.lo scim_iconv.lo > scim_imengine.lo scim_imengine_module.lo scim_lookup_table.lo scim_module.lo > scim_object.lo scim_panel_agent.lo scim_panel_client.lo scim_private.lo > scim_signals.lo scim_slot.lo scim_socket.lo scim_transaction.lo > scim_utility.lo libltdlc.la > > *** Warning: Trying to link with static lib archive /usr/local/lib/libiconv.a. > *** I have the capability to make that library automatically link in when > *** you link to this library. But I can only do this if you have a > *** shared version of the library, which you do not appear to have > *** because the file extensions .a of this argument makes me believe > *** that it is just a static archive that I should not used here. > c++ -shared -fPIC -DPIC .libs/scim_backend.o .libs/scim_chartraits.o > .libs/scim_compose_key.o .libs/scim_config_base.o .libs/scim_config_module.o > .libs/scim_connection.o .libs/scim_debug.o .libs/scim_event.o > .libs/scim_filter.o .libs/scim_filter_module.o .libs/scim_filter_manager.o > .libs/scim_frontend.o .libs/scim_frontend_module.o .libs/scim_global_config.o > .libs/scim_helper.o .libs/scim_helper_manager.o .libs/scim_helper_module.o > .libs/scim_hotkey.o .libs/scim_iconv.o .libs/scim_imengine.o > .libs/scim_imengine_module.o .libs/scim_lookup_table.o .libs/scim_module.o > .libs/scim_object.o .libs/scim_panel_agent.o .libs/scim_panel_client.o > .libs/scim_private.o .libs/scim_signals.o .libs/scim_slot.o > .libs/scim_socket.o .libs/scim_transaction.o .libs/scim_utility.o > -Wl,--whole-archive ./.libs/libltdlc.a -Wl,--no-whole-archive -lstdc++ > -L/usr/local/lib -liconv -lintl -o .libs/libscim-1.0.so.9.0 > === > > Nevermind, this is just a warning. > If you are using SCIM with no problem, there's no problem.
in this case, it is not a problem because -liconv is already part of the link command. if -liconv weren't aleady in the link command, then there would be a problem, because libtool will _not_ link a static library into a shared object. it would be best to change '/usr/local/lib/libiconv.a' to '-L/usr/local/lib -liconv'. presumably, this is coming from some configure generated variable, but I have not looked at this port. -- <[EMAIL PROTECTED]>
