BIND 10 #2661: handle space in "-L /path/to/lib" output from python-config

[BIND 10 Development]

#2661: handle space in "-L /path/to/lib" output from python-config
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  build system  |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130219
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  2             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:9 jelte]:

 > My python3.2-config --ldflags output is:
 > -L/usr/lib/python3.2/config-3.2mu -lpthread -ldl -lutil -lm
 -lpython3.2mu -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
 >
 > And I have been testing several variations of sed in scripts and
 configure.ac; the problems here seems to be that the blockquotes don't
 survive (it works in raw shellscript but not in configure.ac).

 Hmm, strange...

 > Removing spaces after -l is in principle unnecessary in itself, but at
 least it would always match if there is something useful in the -config
 output.
 >
 > The only question is whether that would break with any other version of
 autoconf :)

 Okay, in that case I'd suggest using `[]`.  At least it doesn't cause
 disruption for me either, and we can confirm it with buildbots, too.
 Also, even if there's some portability issues depending on the version
 of autoconf we can't check ourselves, it's less critical because
 release versions are provided with pre-generated configure script.

 As for the case where -L doesn't exist, we can actually ignore the
 entire output because this part of the script only extracts -Lxxx
 values.  I clarified that with revised comments.

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