View previous topic :: View next topic |
Author |
Message |
beyondkmp n00b
Joined: 14 Jan 2014 Posts: 28
|
Posted: Tue Jan 14, 2014 7:32 am Post subject: when I install stardict, I meet :could not read symbols |
|
|
Code: |
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: note: 'g_module_symbol' is defined in DSO /usr/lib64/libgmodule-2.0.so.0 so try adding it to the linker command line
/usr/lib64/libgmodule-2.0.so.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[4]: *** [stardict] Error 1
make[4]: Leaving directory `/var/tmp/portage/app-text/stardict-3.0.3-r2/work/stardict-3.0.3/dict/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/app-text/stardict-3.0.3-r2/work/stardict-3.0.3/dict/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/app-text/stardict-3.0.3-r2/work/stardict-3.0.3/dict'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/app-text/stardict-3.0.3-r2/work/stardict-3.0.3/dict'
make: *** [all-recursive] Error 1
* ERROR: app-text/stardict-3.0.3-r2::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=app-text/stardict-3.0.3-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-text/stardict-3.0.3-r2::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-text/stardict-3.0.3-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-text/stardict-3.0.3-r2/temp/environment'.
* Working directory: '/var/tmp/portage/app-text/stardict-3.0.3-r2/work/stardict-3.0.3'
* S: '/var/tmp/portage/app-text/stardict-3.0.3-r2/work/stardict-3.0.3'
|
Thank you! If you want to any information ,tell me. I just use gentoo for a month |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Tue Jan 14, 2014 8:48 am Post subject: |
|
|
That probably says, that whatever is getting linked is getting underlinked.
Lately it's a quite common problem in many packages. |
|
Back to top |
|
|
beyondkmp n00b
Joined: 14 Jan 2014 Posts: 28
|
Posted: Tue Jan 14, 2014 8:53 am Post subject: |
|
|
VoidMage wrote: | That probably says, that whatever is getting linked is getting underlinked.
Lately it's a quite common problem in many packages. |
Thank you! You mean this is not the problem of this software, it is os's problems? |
|
Back to top |
|
|
joekyo n00b
Joined: 11 Jan 2014 Posts: 4
|
Posted: Sun Mar 02, 2014 4:48 am Post subject: |
|
|
Code: | LDFLAGS='-lgmodule-2.0' emerge stardict |
this works for me |
|
Back to top |
|
|
beyondkmp n00b
Joined: 14 Jan 2014 Posts: 28
|
Posted: Mon Mar 03, 2014 1:28 am Post subject: |
|
|
joekyo wrote: | Code: | LDFLAGS='-lgmodule-2.0' emerge stardict |
this works for me |
Thank you very much!!! It also works for me. Could you explain for me? |
|
Back to top |
|
|
joekyo n00b
Joined: 11 Jan 2014 Posts: 4
|
Posted: Mon Mar 03, 2014 5:20 pm Post subject: |
|
|
Quote: | /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: note: 'g_module_symbol' is defined in DSO /usr/lib64/libgmodule-2.0.so.0 so try adding it to the linker command line |
'g_module_symbol' is defined in libgmodule-2.0.so.0, but seems it hasn't been loaded.
i guess maybe there is ebuild file has problem.
anyway, to tell linker to load that library file, you can use LDFLAGS. |
|
Back to top |
|
|
|