Opened 16 years ago
Closed 15 years ago
#3997 closed bug (fixed)
Subversion 1.6.2 from Optionalpackage fails to start
Reported by: | mt | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | planche2k@… | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
Subversion 1.6.2 from Optionalpackage fails to start. (Tested in hrev30957)
Welcome to the Haiku shell. ~> svn runtime_loader: /boot/common/lib/libneon.so.27.1.4: Could not resolve symbol 'libiconv_set_relocation_prefix' resolve symbol "libiconv_set_relocation_prefix" returned: -2147478780 runtime_loader: /boot/common/lib/libneon.so.27.1.4: Troubles relocating: Symbol not found ~>
Change History (5)
follow-up: 2 comment:1 by , 16 years ago
comment:2 by , 16 years ago
Replying to stippi:
Please provide more information what versions of libiconv.so you have installed in which places. Thanks!
It seems two version of libiconv installed on my system.
~> ls -l /boot/common/lib/libiconv* -rw-r--r-- 1 baron root 918 Jun 4 21:47 /boot/common/lib/libiconv.la lrwxrwxrwx 1 baron root 17 Jun 4 21:47 /boot/common/lib/libiconv.so -> libiconv.so.2.5.0 lrwxrwxrwx 1 baron root 17 Jun 4 21:47 /boot/common/lib/libiconv.so.2 -> libiconv.so.2.5.0 -rw-r--r-- 1 baron root 1124586 Jun 4 21:47 /boot/common/lib/libiconv.so.2.5.0 ~> ls -l /boot/system/lib/libiconv* -rwxr-xr-x 1 baron root 1043075 Jun 4 21:47 /boot/system/lib/libiconv.so ~>
I clean build hrev30957 gcc4/gcc2 hybrid mode with Optinalpackage (Development, subversion etc..).
comment:3 by , 16 years ago
The problem does indeed occur on the gcc4/gcc2 hybrid build only. The runtime loader does search the /system/lib/gcc2 directory before /boot/common/lib (since svn is a gcc2 build) and therefore finds the wrong libiconv.so (version 1.12 instead of 1.13). Creating a /boot/common/lib/gcc2/ and linking the ../libiconv.so there, solves the issue. I see two problems:
- libneon's dependency is "libiconv.so", although it correctly should be "libiconv.so.2". At least that's the soname of the correct one.
- The libiconv.so generated by the build system is not properly versioned. Though that might break things again. I don't get libiconv's naming scheme -- supposedly 1.13 is only a minor version update, so it would be "libiconv.so.2", too.
Besides fixing those two issues, I guess OptionalPackages has to add symlinks as the one above for hybrid builds.
comment:4 by , 16 years ago
Cc: | added |
---|
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
this has been fixed one ticket #4363
Please provide more information what versions of libiconv.so you have installed in which places. Thanks!