Whoops, you are absolutely right. I did not do the ash testing correctly, but I figured out why and retested. The patch I gave you did not work under ash, and that was because of the extra back slash quotes, just like you say.
<br><br>I tested this new patch you sent under ash and I also tested it with dash - it works there too.<br><br>I have one more change for your patch - the comment about "scripts/config/mkconfigs" should be "scripts/mkconfigs". This comment gets put into
bbconfigopts.h. I regenerated the diff with this additional change and attached it as "4.sed.patch". I also fixed the awk-only version and retested it under ash. I attached it as "4.awk.patch". I personally like the awk-only version a little better because it is only one invocation vs. three invocations and two pipes for the sed | grep | awk version, and maybe more because it is a slick awk one-liner - but its trivial, really. It's just a shell script that is part of the build process. They both work to get the job done so they both work for me.
<br><br>Thanks<br><br>Brion<br><br><div><span class="gmail_quote">On 2/3/07, <b class="gmail_sendername">Denis Vlasenko</b> <<a href="mailto:vda.linux@googlemail.com">vda.linux@googlemail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Saturday 03 February 2007 06:14, Brion Finlay wrote:<br>> The fix that could be made to scripts/mkconfigs in order to work more<br>> generally, be less indirect, and avoid some of the backslash quoting would<br>> be to eliminate the echo "`...`" construction and just execute the command
<br>> directly. That is, change this:<br>><br>> echo "`sed 's/\"/\\\\\"/g' $config | grep "^#\? \?CONFIG_" | awk '{print<br>> "\\"" $0 "\\\\n\\"";}'`"
<br>><br>> to this:<br>><br>> sed 's/\"/\\\\\"/g' $config | grep "^#\? \?CONFIG_" | awk '{print "\"" $0<br>> "\\n\"";}'<br>><br>> I tested this change under bash and dash and it works in both shells.
<br><br>But it doesn't work for me. ;) Your sed should have three \\\ instead of five.<br><br>Can you try the attached patch? Will apply if it also works for you.<br>--<br>vda<br><br><br></blockquote></div><br>