On 3/25/07, yayo <[EMAIL PROTECTED]> wrote: > I've used this: > > sed 's/@sh/sh/' Makefile.SH > temp > mv temp Makefile.SH
Yes, that's the right way. I forgot that we don't know what sed is being used at that point. The sed you install later takes -i as an argument. > Anyway, there's no difference: the command "sh ./makedir lib/auto" > doesn't seems to produce an output. IT IS a silent command. > It just fails to make the dir. They make the errors silent in the script. I wish they wouldn't do that. If you want to see what the error would look like, just run "mkdir" with no arguments. > I've investigated a bit making some tests. > It doesn't seems to be the makedir executable which fails, but the 'sh' part. > "./makedir lib/auto" works. > "sh ./makedir lib/auto" doesn't. OK, that helps some. Using the first way, you're using /bin/sh from the Knoppix CD. The second way, you're using /tools/bin/sh, which is the bash you installed earlier. Something's going wrong with bash (I think). Can you try this test? $ cat > test.sh << "EOF" #!/tools/bin/sh set ./lib ./lib/auto for dir do echo $dir done EOF $ /tools/bin/sh -x ./test.sh The output should be: + set ./lib ./lib/auto + for dir in '"$@"' + echo ./lib ./lib + for dir in '"$@"' + echo ./lib/auto ./lib/auto > now, you are the experienced users: > so this not-working 'sh' means... what? >:? It just means you're running the sh shell, which is a symbolic link to bash. You're just being explicit about what shell you're using to run that script. > (note: I've still not get over this perl step, > because I was busy doing else in these days. > I just made these tests to understand the problem.) You can workaround the problem by running "mkdir lib/auto" before you run "make perl utilites", but I'd appreciate if you could help debug this since I can't make it fail myself. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
