BIND 10 #149: review: auto detect libpython fails for netbsd and linux

[BIND 10 Development]

#149: review: auto detect libpython fails for netbsd and linux
--------------------------+-------------------------------------------------
 Reporter:  jinmei        |        Owner:  jreed   
     Type:  defect        |       Status:  assigned
 Priority:  minor         |    Milestone:          
Component:  Unclassified  |   Resolution:          
 Keywords:                |    Sensitive:  0       
--------------------------+-------------------------------------------------
Changes (by jinmei):

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


Comment:

 Replying to [comment:2 jreed]:
 > patch has:
 > +       # add any '-L..." flags to PYTHON_INCLUDES
 > Should that say PYTHON_LDFLAGS instead?

 Good catch, fixed in r1732.

 > Also is that -L from python-config actually provide location that
 provides correct needed library?
 > (For example, my library is under the $prefix/lib and it is different
 from what is under the config directory.)

 I don't understand the question...

  - which one do you mean by -L from python-config?  from python-config
 --ldflags?  or from --pefix (+ /lib?)
  - whether it's "correct" or not is in general a difficult question when
 we do auto-detect things, because ultimately only the user know what's
 "correct".  at least the configure script perfroms AC_CHECK_LIB() with the
 identified parameters.  and for the script, the definition of "correct" is
 the AC_CHECK_LIB() test passes.  Do you mean it's not sufficient?  Or do
 you mean we need an explicit switch so that the user can specify the
 "really correct" path?

-- 
Ticket URL: <http://bind10.isc.org/ticket/149#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development