New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PATCH 5.5.660] $@ unsafe in Configure sed arguments #1218
Comments
From domo@computer.orgCreated by domo@computer.orgThis has been going on a while, but, as it didn't actually stop me In a number of cases, Configure uses '@' as a delimiter in arguments As shell quoting problems are hell to trace, I'm simply attaching a Oh, yes: some test problems for MachTen and 5.5.660. Report Inline Patch--- perl5.5.660/Configure-as-received Tue Feb 22 10:19:52 2000
+++ perl5.5.660/Configure Wed Feb 23 17:18:52 2000
@@ -2403,12 +2403,12 @@
: specified already.
case "$hintfile" in
''|' ')
- file=`echo "${osname}_${osvers}" | $sed -e 's@\.@_@g' -e 's@_$@@'`
+ file=`echo "${osname}_${osvers}" | $sed -e 's%\.%_%g' -e 's%_$%%'`
: Also try without trailing minor version numbers.
- xfile=`echo $file | $sed -e 's@_[^_]*$@@'`
- xxfile=`echo $xfile | $sed -e 's@_[^_]*$@@'`
- xxxfile=`echo $xxfile | $sed -e 's@_[^_]*$@@'`
- xxxxfile=`echo $xxxfile | $sed -e 's@_[^_]*$@@'`
+ xfile=`echo $file | $sed -e 's%_[^_]*$%%'`
+ xxfile=`echo $xfile | $sed -e 's%_[^_]*$%%'`
+ xxxfile=`echo $xxfile | $sed -e 's%_[^_]*$%%'`
+ xxxxfile=`echo $xxxfile | $sed -e 's%_[^_]*$%%'`
case "$file" in
'') dflt=none ;;
*) case "$osvers" in
@@ -3743,7 +3743,7 @@
libsfound="$libsfound $xxx"
yyy=`basename $xxx`
libsfiles="$libsfiles $yyy"
- yyy=`echo $xxx|sed "s@/$yyy\\$@@"`
+ yyy=`echo $xxx|sed "s%/$yyy\\$%%"`
case " $libsdirs " in
*" $yyy "*) ;;
*) libsdirs="$libsdirs $yyy" ;;
@@ -5958,7 +5958,7 @@
. ./getfile
usedl="$define"
: emulate basename
- dlsrc=`echo $ans | $sed -e 's@.*/\([^/]*\)$@\1@'`
+ dlsrc=`echo $ans | $sed -e 's%.*/\([^/]*\)$%\1%'`
$cat << EOM
Perl Info
|
Migrated from rt.perl.org#2202 (status was 'resolved')
Searchable as RT2202$
The text was updated successfully, but these errors were encountered: