BIND 10 #148: bind10_dns and bind10_xfr find needed libboost_python and libpython

[BIND 10 Development]

#148: bind10_dns and bind10_xfr find needed libboost_python and libpython
--------------------------+-------------------------------------------------
 Reporter:  jreed         |        Owner:  jreed   
     Type:  defect        |       Status:  assigned
 Priority:  major         |    Milestone:          
Component:  Unclassified  |   Resolution:          
 Keywords:                |    Sensitive:  0       
--------------------------+-------------------------------------------------
Changes (by jinmei):

  * owner:  => jreed
  * status:  new => assigned


Comment:

 Replying to [ticket:148 jreed]:
 > Build bind10_dns and bind10_xfr with RPATH details so can find
 libboost_python and libpython so don't have to use LD_LIBRARY_PATH for
 example. (I understand this is system specific.)

 Please review branch/trac148.  The only diff is in configure.ac which can
 be retrieved by:
 {{{
 % svn diff -r 1771:1789
 svn+ssh://bind10.isc.org/svn/bind10/branches/trac148
 }}}

 I tried in this patch to make the configure script even uglier so that it
 will automagically set up everything:

  1. it first tries to run a test program without any special options.  in
 some cases that's sufficient.
  2. otherwise, if -R linker option is available it tries to embed the path
 to the boost libraries in executable and run the test program.  If it
 works, choose this option.
  3. otherwise, if static version of library is available (e.g
 libboost_python.a), try to use it.  This is a last resort option because
 the absolute path to the library needs to be guessed and the resulting
 binary may be bigger.

 Alternatively, we could let the user specify the availability and use of
 the -R option, e.g.,
 {{{
 % ./configure --with-boost-rpath=/opt/local/lib
 }}}
 and/or explicitly specify the availability and use of static version of
 library:
 {{{
 % ./configure --with-boost-system-
 staticlib=/opt/local/lib/libbost_system.a
 }}}

 This is a tradeoff issue between amount of manual configuration
 (especially when something goes wrong) and complexity of the configure
 script.  At this stage I think we should prioritize lower the bar for
 introduction and chose the latter option.

-- 
Ticket URL: <https://bind10.isc.org/ticket/148#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development