Re: dpkg-shlibdeps couldn't find library ... warning vs error

2019-06-28 Thread Guillem Jover
Hi! [ Just rereading my reply, I should stop sending mail with a sleep deprived brain, sorry! :) ] On Fri, 2019-06-28 at 08:09:11 -0400, Crim, Christopher wrote: > On Thursday, June 27, 2019 9:09:34 PM EDT Guillem Jover wrote: > > On Wed, 2019-06-26 at 14:58:34 -0400, Crim, Christopher wrote: >

Re: dpkg-shlibdeps couldn't find library ... warning vs error

2019-06-28 Thread Crim, Christopher
Thank you Guillem for your response. I have a few followups that I have put inline below. On Thursday, June 27, 2019 9:09:34 PM EDT Guillem Jover wrote: > Hi! > > On Wed, 2019-06-26 at 14:58:34 -0400, Crim, Christopher wrote: > > I am trying to understand the regex rules in the function split_s

Re: dpkg-shlibdeps couldn't find library ... warning vs error

2019-06-27 Thread Russ Allbery
Guillem Jover writes: > On Wed, 2019-06-26 at 14:58:34 -0400, Crim, Christopher wrote: >> I have tried searching for inforamtion related to to naming conventions >> for shared library names but the best I can come up with is that they >> need to be prefixed with "lib" and suffixed with ".so" and

Re: dpkg-shlibdeps couldn't find library ... warning vs error

2019-06-27 Thread Guillem Jover
Hi! On Wed, 2019-06-26 at 14:58:34 -0400, Crim, Christopher wrote: > I am trying to understand the regex rules in the function split_soname from > dkpg-shlibdeps.pl. Working with an old corporate code base that has yet to > adopt any versioning, all of the shared objects are named .so. When >

dpkg-shlibdeps couldn't find library ... warning vs error

2019-06-26 Thread Crim, Christopher
I am trying to understand the regex rules in the function split_soname from dkpg-shlibdeps.pl. Working with an old corporate code base that has yet to adopt any versioning, all of the shared objects are named .so. When attempting to package on a box that does not yet have the dependent package