BIND 10 #2817: message "sed: command garbled: s/\([ \t]*-L\)[ ]*\([^ \t]*[ \t]*\)/\1\2/pg" on Solaris builds

[BIND 10 Development]

#2817: message "sed: command garbled: s/\([ \t]*-L\)[ ]*\([^ \t]*[ \t]*\)/\1\2/pg"
on Solaris builds
-------------------------------------+-------------------------------------
            Reporter:  cas           |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  build system  |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130319
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  3             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 it's actually not the regex itself it is tripping over, it's the modifier
 flags (/pg); I can't really find much documentation of this, except that
 for some other combination the order does indeed matter (and if that is
 true in this case too, p should be last anyway).

 {{{
 jelte at sol-10:~
 > echo "-La -L b -Lc -L d" | sed -ne 's/\([ ]*-L\)[ ]*\([^ \t]*[
 \t]*\)/\1\2/pg'
 sed: command garbled: s/\([ ]*-L\)[ ]*\([^ \t]*[ \t]*\)/\1\2/pg
 jelte at sol-10:~
 > echo "-La -L b -Lc -L d" | sed -ne 's/\([ ]*-L\)[ ]*\([^ \t]*[
 \t]*\)/\1\2/gp'
 -La -L b -Lc -L d
 }}}

 Flipped them, and replaced all calls to sed with $(SED)

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