[MacPorts] #28662: baresip 0.1.0

[MacPorts]

#28662: baresip 0.1.0
-------------------------+--------------------------------------------------
  Reporter:  aeh@…       |       Owner:  ryandesign@…           
      Type:  submission  |      Status:  reopened               
  Priority:  Normal      |   Milestone:                         
 Component:  ports       |     Version:  1.9.2                  
Resolution:              |    Keywords:  SIP,SDP,RTP            
      Port:  baresip     |  
-------------------------+--------------------------------------------------

Comment(by aeh@…):

 I have investigated the problem with the module loading, and found the
 issue.

 it appears that the identity of each .so module was change during the
 build,
 for example:

 {{{
 $ otool -D g711.so
 g711.so:
 /usr/local/lib/libre.dylib
 }}}


 the install should be the same as the module name (with our without path,
 I am not sure)

 it appears that the new install name is coming from SH_LFLAGS which adds
 the -install_name
 option in this patch to libre:

 {{{
 --- mk/re.mk.orig       2010-11-03 06:34:14.000000000 -0500
 +++ mk/re.mk    2011-03-28 01:10:55.000000000 -0500
 @@ -271,6 +271,7 @@
         AR              := ar
         AFLAGS          := cru
         LIB_SUFFIX      := .dylib
 +       SH_LFLAGS       += -install_name $(PREFIX)/lib/libre$(LIB_SUFFIX)
         ARCH            := $(shell echo $(MACHINE) | \
                                 sed -e 's/\([^-]*\)-.*/\1/')
  endif
 @@ -488,9 +488,6 @@
 }}}


 the makefile variable $(SH_LFLAGS) is used both by libre and also by some
 applications
 linking to libre, so we should probably find a better solution for this.

 is the -install_name option really necessary for working operation? or can
 we remote it.
 without the additional patch (no -install_name) both libre and baresip
 installs and runs
 successfully (also modules are loaded fine).

-- 
Ticket URL: <https://trac.macports.org/ticket/28662#comment:15>
MacPorts <http://www.macports.org/>
Ports system for Mac OS