pkg-config-0.20, Solaris 2.8 /usr/bin/sed doesn't appear to remove all of the trailing blanks in the check tests, but /usr/xpg4/bin/sed does: % R=$(env PKG_CONFIG_PATH=. ../pkg-config --static --libs simple) % echo ">$R<" >-lsimple -lm < % echo '>'$(echo "$R" | /usr/bin/sed -e 's,^[[:space:]]*,,' -e 's,[[:space:]]*$,,')'<' >-lsimple -lm < % echo '>'$(echo "$R" | /usr/xpg4/bin/sed -e 's,^[[:space:]]*,,' -e 's,[[:space:]]*$,,')'<' >-lsimple -lm<
I wonder if the problem here is that [[:space:]] is not recognized at all? What if you do R=" $R" after the initial assignment...does the leading space have the same problem as the trailing one you noticed? Sounds like "checking for non-broken sed..." is a good ./configure test, and then see how sed performs, or else check $host. A bad idea is to use "no ~root dir" as a surrogate test and force /usr/xpg4/bin/sed based on that, since other platforms may not have ~root.
% echo ">$R<" >-lsimple -lm < % R=" $R" % echo ">$R<" > -lsimple -lm < % echo '>'$(echo "$R" | /usr/bin/sed -e 's,^[[:space:]]*,,' -e 's,[[:space:]]*$,,')'<' > -lsimple -lm < looks like [[:space:]] isn't recognized at all.
This should be fixed in the latest version where we set PATH to what getconf PATH returns.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.