search

kongp3 / stardict-3

Automatically exported from code.google.com/p/stardict-3
GNU General Public License v3.0
0 stars 0 forks source link

Undefined symbols _g_module_close, _g_module_open, _g_module_symbol #59

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. compile stardict 3.0.4 on OS X

What is the expected output? What do you see instead?
Expected successful compile but got:

Undefined symbols for architecture x86_64:
  "_g_module_close", referenced from:
      StarDictPluginBase::~StarDictPluginBase() in libstardict.a(pluginmanager.o)
      StarDictPlugins::get_plugin_info(char const*, StarDictPlugInType&, std::string&, bool&) in libstardict.a(pluginmanager.o)
      StarDictPlugins::load_plugin(char const*) in libstardict.a(pluginmanager.o)
  "_g_module_open", referenced from:
      StarDictPlugins::get_plugin_info(char const*, StarDictPlugInType&, std::string&, bool&) in libstardict.a(pluginmanager.o)
      StarDictPlugins::load_plugin(char const*) in libstardict.a(pluginmanager.o)
  "_g_module_symbol", referenced from:
      StarDictPluginBase::~StarDictPluginBase() in libstardict.a(pluginmanager.o)
      StarDictPlugins::get_plugin_info(char const*, StarDictPlugInType&, std::string&, bool&) in libstardict.a(pluginmanager.o)
      StarDictPlugins::load_plugin(char const*) in libstardict.a(pluginmanager.o)
      StarDictMiscPlugin::on_mainwin_finish() in libstardict.a(pluginmanager.o)
ld: symbol(s) not found for architecture x86_64

What version of the product are you using? On what operating system?
stardict 3.0.4 on OS X 10.8.5 with Xcode 4.6.3 and its Apple LLVM version 4.2 
(clang-425.0.28) (based on LLVM 3.2svn)

Please provide any additional information below.
Adding -lgmodule-2.0 to the LIBS environment variable fixes the problem.

Original issue reported on code.google.com by ryandesi...@gmail.com on 24 Sep 2013 at 4:30

GoogleCodeExporter commented 8 years ago 
Just use the newest code in hg source repository. It is already fixed!

Original comment by huzheng...@gmail.com on 30 Oct 2013 at 9:12