Databases
StackOverflow2013
Postsdbo
POICU 49 Built on a Debian System Fails to Load libicudata.so
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POICU 49 Built on a Debian System Fails to Load libicudata.so
    primarykey
    data
    text
    <p>Recently I compiled ICU 49.1.2 on two systems - one Ubuntu and one Debian-based ("Wheezy" for the Raspberry Pi). The Ubuntu system works, but the RPi system reports an error when I try to run any of the ICU executables or when I link it in with my application:</p> <pre><code>me@raspberrypi ~/icu/source $ genrb -V genrb: error while loading shared libraries: libicudata.so.49: cannot open shared object file: No such file or directory </code></pre> <p>I've verified the libraries exist:</p> <pre><code>me@raspberrypi ~/icu/source $ find / -name 'libicudata.so*' 2&gt;/dev/null /usr/local/lib/libicudata.so /usr/local/lib/libicudata.so.49.1.2 /usr/local/lib/libicudata.so.49 </code></pre> <p>And that pkg-config confirms this:</p> <pre><code>me@raspberrypi ~/icu/source $ pkg-config --libs-only-L icu-uc -L/usr/local/lib </code></pre> <p>I also made sure to run <code>sudo ldconfig</code> after installing ICU. I even tried running <code>make check</code> on the failing system:</p> <pre><code>LD_LIBRARY_PATH=../../lib:../../stubdata:../../tools/ctestfw:$LD_LIBRARY_PATH ./../../bin/uconv -f ibm-37 ./samples/ibm-37-test.txt ./../../bin/uconv: can not initialize ICU. status = U_FILE_ACCESS_ERROR make[2]: *** [check-local] Error 1 make[2]: Leaving directory `/home/uli/icu/source/extra/uconv' make[1]: *** [check-recursive] Error 2 make[1]: Leaving directory `/home/uli/icu/source/extra' make: *** [check-recursive] Error 2 </code></pre> <p>As far as I can tell, the systems are identical in terms of locations and presence of the necessary files. It just appears that the Debian-based Raspberry Pi insists on looking somewhere else (presumably /usr/lib) for libicudata.so instead of /usr/local/lib. I could change the --prefix on the ./configure script to fix the problem, but I'd like to understand why one system worked and the other did not.</p> <p><strong>Update</strong></p> <p>Well, I thought I could fix the problem by changing the '--prefix' parameter to the ./configure script, but it turns out that doesn't work. I have libicudata.so.49 in /usr/lib and /usr/local/lib, but ICU still can't find the libraries.</p> <p>I also tried creating a "Hello World" program that just included the ICU libraries to see what would happen. Same failures:</p> <pre><code>me@raspberrypi ~ $ gcc -licudata -licuuc helloworld.c me@raspberrypi ~ $ ./a.out ./a.out: error while loading shared libraries: libicudata.so.49: cannot open shared object file: No such file or directory me@raspberrypi ~ $ ldd a.out /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0xb6f41000) libicudata.so.49 =&gt; not found libicuuc.so.49 =&gt; /usr/local/lib/libicuuc.so.49 (0xb6df8000) libc.so.6 =&gt; /lib/arm-linux-gnueabihf/libc.so.6 (0xb6cc9000) libicudata.so.49 =&gt; not found libpthread.so.0 =&gt; /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6caa000) libdl.so.2 =&gt; /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6c9f000) libstdc++.so.6 =&gt; /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb6bd2000) libm.so.6 =&gt; /lib/arm-linux-gnueabihf/libm.so.6 (0xb6b61000) libgcc_s.so.1 =&gt; /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb6b39000) /lib/ld-linux-armhf.so.3 (0xb6f4d000) </code></pre> <p><strong>Update 2</strong></p> <p>I'm recompiling right now with the LDFLAGSICUDT flag commented out (The RPi is a little slow on the compile).</p> <p>As for the other comment, here is the output from the file command:</p> <pre><code>me@raspberrypi ~ $ file /usr/local/lib/libicudata.so* /usr/local/lib/libicudata.so: symbolic link to `libicudata.so.49.1.2' /usr/local/lib/libicudata.so.49: symbolic link to `libicudata.so.49.1.2' /usr/local/lib/libicudata.so.49.1.2: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xfb336da457f28964a6161af4d7b07902882d6fa8, not stripped </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGrandAdmiral
    1. USGrandAdmiral
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POICU 49 Built on a Debian System Fails to Load libicudata.so
      1. USGrandAdmiral
      1. VTBountyStart
    2. VO
      singulars
      1. POICU 49 Built on a Debian System Fails to Load libicudata.so
      1. This table or related slice is empty.
      1. VTUpMod
    1. COProbably the ldconfig paths are setup differently on the two systems. Have you compared the contents of /etc/ld.so.conf and /etc/ld.so.conf.d? Probably /usr/local/lib is not included there on the Debian system.
      singulars
      1. POICU 49 Built on a Debian System Fails to Load libicudata.so
      1. USTeTeT
    2. COThe /etc/ld.so.conf.d/libc.conf file on both systems reports /usr/local/lib.
      singulars
      1. POICU 49 Built on a Debian System Fails to Load libicudata.so
      1. USGrandAdmiral
    3. COI just took a look at the icu package on 12.04 LTS. It's an older version (4.8), but there the LDFLAGSICUDT flags are commented out in source/config/mh-linux and a comment states that linking it as data only would cause too many problems.
      singulars
      1. POICU 49 Built on a Debian System Fails to Load libicudata.so
      1. USTeTeT
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload