| commit | 138f28aaafc3bd3087efbc25f49f752c66d14157 | |
| author | Daniel Borkmann <dborkman@redhat.com> | |
| Fri, 12 Jul 2013 08:52:07 +0000 (12 10:52 +0200) | ||
| committer | Daniel Borkmann <dborkman@redhat.com> | |
| Fri, 12 Jul 2013 08:52:07 +0000 (12 10:52 +0200) | ||
| tree | a2f83cbb692fc020ee1eb71379c94901989b8ff6 | treesnapshot (tar.gz zip) |
| parent | 8f92276156b1fbdeebd085b731ed4aeab3960432 | commitdiff |
configure: do not use bash's expr match
It looks like there are some incompatibilities in bash's expr match
among different versions. Using set -x, gives us on bash 4.2.45:
+ TOOLS=' netsniff-ng trafgen ifpps bpfc'
+ for tool in '$_tools'
+ case "$tool" in
++ expr match '"curvetun' 'astraceroute"' '$1'
expr: syntax error
+ m=
+ '[' '' == 0 ']'
So rather avoid using "expr match" and switch to "case" for substring
matching, which should be more portable.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
It looks like there are some incompatibilities in bash's expr match
among different versions. Using set -x, gives us on bash 4.2.45:
+ TOOLS=' netsniff-ng trafgen ifpps bpfc'
+ for tool in '$_tools'
+ case "$tool" in
++ expr match '"curvetun' 'astraceroute"' '$1'
expr: syntax error
+ m=
+ '[' '' == 0 ']'
So rather avoid using "expr match" and switch to "case" for substring
matching, which should be more portable.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
| configure | diffblobblamehistory |