SCons build problems - SONAME


Daniel Pocock
 

The SCons build is not setting SONAME for the shared libs (this was set
correctly with the autotools build), e.g.

$ objdump -p ./objdir/mama/c_cpp/src/c/.libs/libmama.so |grep SONAME

doesn't give any output. SONAME is really important when packaging.


It appears correctly for 2.2.2.1:

$ objdump -p /usr/lib/x86_64-linux-gnu/libmama.so.0 | grep SONAME
SONAME libmama.so.0


Damian Maguire
 

Thanks for raising this Daniel, I can see the issue you're talking about, and it appears to be an issue with the way SCons builds it's shared libraries. It'll probably require a bit more digging on my part, but we may have to implement a bit of a custom solution to make this work in the same way as libtool does. As noted in the other thread, would you be able to raise a bugzilla ticket for this so we can track it more easily? 

Cheers, 

D


On Sat, May 3, 2014 at 7:26 AM, Daniel Pocock <daniel@...> wrote:




The SCons build is not setting SONAME for the shared libs (this was set
correctly with the autotools build), e.g.

$ objdump -p ./objdir/mama/c_cpp/src/c/.libs/libmama.so |grep SONAME

doesn't give any output.  SONAME is really important when packaging.


It appears correctly for 2.2.2.1:

$ objdump -p /usr/lib/x86_64-linux-gnu/libmama.so.0 | grep SONAME
  SONAME               libmama.so.0


_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev