strigi weirdness on 'make install'

Benjamin Reed rangerrick at gmail.com
Mon Mar 19 04:00:08 CET 2007


I'm trying to do a "make install" on the latest strigi and I get this:

---(snip!)---
...
-- Installing /opt/kde4-deps/include/strigi/fieldtypes.h

                                                              --
Installing /opt/kde4-deps/lib/libstreamanalyzer.0.3.11.dylib

                                                           --
Installing /opt/kde4-deps/lib/strigi/strigita_xpm.so


install_name_tool: can't open file:
/opt/kde4-deps/lib/strigi/strigita_xpm.0.so (No such file or
directory)
                                    -- Installing
/opt/kde4-deps/bin/deepfind

                                                -- Installing
/opt/kde4-deps/bin/deepgrep
...
---(snip!)---

It looks like it created a strigita_xpm.so file but then when it tries
to do the install_name magic it fails.  Doing an otool -L on the
binary shows this:

---(snip!)---
/opt/kde4-deps/lib/strigi/strigita_xpm.so:
        /Users/ranger/cvs/packages/compile.build/strigi/src/streamanalyzer/libstreamanalyzer.0.dylib
(compatibility version 0.0.0, current version 0.0.0)
        /Users/ranger/cvs/packages/compile.build/strigi/src/streams/libstreams.0.dylib
(compatibility version 0.0.0, current version 0.0.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.2.3)
        /usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0,
current version 1.0.2)
        /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7,
current version 0.9.7)
        /opt/kde4-deps/lib/libiconv.2.dylib (compatibility version
7.0.0, current version 7.0.0)
        /opt/kde4-deps/lib/libxml2.2.dylib (compatibility version
9.0.0, current version 9.22.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 88.3.3)
        /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0,
current version 7.4.0)
        /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0,
current version 1.0.0)
---(snip!)---

Which means the bad paths are in the .so file.

$ cmake --version
cmake version 2.4-patch 5


More information about the Kde-buildsystem mailing list