- Added debian/libosmosim0.install - Added libosmosim definition in debian/control --- debian/control | 6 ++++++ debian/libosmosim0.install | 1 + 2 files changed, 7 insertions(+) create mode 100644 debian/libosmosim0.install
diff --git a/debian/control b/debian/control index cde3713..ccc7331 100644 --- a/debian/control +++ b/debian/control @@ -50,6 +50,12 @@ Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: Osmo control library
+Package: libosmosim0 +Section: libs +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends} +Description: Osmo SIM library + Package: libosmocore-dev Section: libdevel Architecture: any diff --git a/debian/libosmosim0.install b/debian/libosmosim0.install new file mode 100644 index 0000000..8f29c4d --- /dev/null +++ b/debian/libosmosim0.install @@ -0,0 +1 @@ +usr/lib/libosmosim*.so.*
On 11/10/2014 12:33 PM, Ciaby wrote: [...] I forgot to mention this warnings at the end of the package generation:
dpkg-shlibdeps: warning: symbol bssgp_prim_cb used by debian/libosmogb3/usr/lib/libosmogb.so.3.0.1 found in none of the libraries. dpkg-shlibdeps: warning: symbol ipa_msg_recv_buffered used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol vector_set used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol tall_vty_vec_ctx used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol vector_set_index used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol cmd_make_strvec used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol ipa_prepend_header used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol vector_free used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol ipa_prepend_header_ext used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol vector_lookup used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol vector_lookup_ensure used by debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: symbol msgb_length used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol talloc_strdup used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol msgb_alloc used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol gsm48_parse_ra used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol talloc_free used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol osmo_panic used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol _talloc_zero used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol osmo_hexdump used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol _talloc_memdup used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: symbol talloc_strndup used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the libraries. dpkg-shlibdeps: warning: 1 similar warning has been skipped (use -v to see it). dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if "debian/libosmosim0/usr/lib/libosmosim.so.0.0.0" were not uselessly linked against it (they use none of its symbols).
Can/should we do something about it? Cheers
Ciaby
On Mon, Nov 10, 2014 at 02:19:23PM -0600, Ciaby wrote:
On 11/10/2014 12:33 PM, Ciaby wrote: [...] I forgot to mention this warnings at the end of the package generation:
dpkg-shlibdeps: warning: symbol bssgp_prim_cb used by debian/libosmogb3/usr/lib/libosmogb.so.3.0.1 found in none of the libraries.
by design... so far.
debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the dpkg-shlibdeps: warning: symbol ipa_msg_recv_buffered used by
it should link to ?? for it.
dpkg-shlibdeps: warning: symbol vector_set used by dpkg-shlibdeps: warning: symbol tall_vty_vec_ctx used by
it should link against libosmovty for it.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: symbol msgb_length used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the
it should link to libosmocore
Can/should we do something about it?
yes. these are issues and violations of link to DSOs that are used principle.
On 11/10/2014 03:42 PM, Holger Hans Peter Freyther wrote:
On Mon, Nov 10, 2014 at 02:19:23PM -0600, Ciaby wrote:
On 11/10/2014 12:33 PM, Ciaby wrote: [...] I forgot to mention this warnings at the end of the package generation:
dpkg-shlibdeps: warning: symbol bssgp_prim_cb used by debian/libosmogb3/usr/lib/libosmogb.so.3.0.1 found in none of the libraries.
by design... so far.
debian/libosmoctrl0/usr/lib/libosmoctrl.so.0.0.0 found in none of the dpkg-shlibdeps: warning: symbol ipa_msg_recv_buffered used by
it should link to ?? for it.
dpkg-shlibdeps: warning: symbol vector_set used by dpkg-shlibdeps: warning: symbol tall_vty_vec_ctx used by
it should link against libosmovty for it.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: symbol msgb_length used by debian/libosmosim0/usr/lib/libosmosim.so.0.0.0 found in none of the
it should link to libosmocore
Can/should we do something about it?
yes. these are issues and violations of link to DSOs that are used principle.
Ok, sounds good. Is the patch good enough to be merged? :) Cheers
Ciaby