[MacPorts] #45664: mecab-java linker error

MacPorts noreply at macports.org
Tue Oct 28 05:35:47 PDT 2014


#45664: mecab-java linker error
-------------------------------+--------------------------------
  Reporter:  mattes.angelus@…  |      Owner:  macports-tickets@…
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.3.2
Resolution:                    |   Keywords:
      Port:  mecab-java        |
-------------------------------+--------------------------------

Comment (by mattes.angelus@…):

 first thank you for the fast reply and formating my text[[br]]
 yes, i have to set the DYLD_LIBRARY_PATH to /opt/local/lib in my java ide
 otherwise i have to use
 {{{
 System.load("/opt/local/lib/libmecab-java.dylib");
 }}}
 instead of
 {{{
 System.loadLibrary("mecab-java");
 }}}
 and this linker error is thrown:
 {{{
 java.lang.UnsatisfiedLinkError:
 org.chasen.mecab.MeCabJNI.new_Tagger__SWIG_1()J
         at org.chasen.mecab.MeCabJNI.new_Tagger__SWIG_1(Native Method)
         at org.chasen.mecab.Tagger.<init>(Tagger.java:144)
         at
 cc.topicexplorer.plugin.japanesepos.preprocessing.implementation.postagger.JPOSMeCab.parseString(JPOSMeCab.java:76)
         at
 cc.topicexplorer.plugin.japanesepos.preprocessing.implementation.postagger.JPOSMeCab.parse(JPOSMeCab.java:57)
         at
 cc.topicexplorer.plugin.japanesepos.preprocessing.tools.test_JPOSMeCab.testDuplicates(test_JPOSMeCab.java:38)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at
 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
         at
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
         at
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
         at
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
         at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
         at
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
         at
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
         at
 org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
         at
 org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
         at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
         at
 org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
         at
 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
         at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
         at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
         at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
         at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
 }}}
 i guess, without DYLD_LIBRARY_PATH it's missing the corresponding libs in
 /opt/local/lib.[[br]]
 with using DYLD_LIBRARY_PATH it takes the corresponding libs from
 /opt/local/lib. but there is no mecabra.dylib, so it searchs for it in
 java.library.path (where /usr/lib/ is in). and so the error occurs... but
 that's just my guess

-- 
Ticket URL: <https://trac.macports.org/ticket/45664#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list