On Mon, Jan 01, 2007 at 04:21:23PM -0800, Arden wrote:
> Hi, and Happy New Year, I hope it's a good one!
 ditto
> 
> I pasted the configure/build script from blfs-book-cvs-html-20061006  
> for Qt-3.3.7 and it immediately exits with:
> 
> bash: ./configure: No such file or directory
> 
> here is the beginning of the script:
> 
> sed -i -e 's:$(QTDIR)/include:&/qt:' \
>         -e 's:$(QTDIR)/lib:&/qt:' \
>      mkspecs/linux*/qmake.conf &&
> 
> bash
> export PATH=$PWD/bin:$PATH &&
> export LD_LIBRARY_PATH=$PWD/lib:$LD_LIBRARY_PATH &&
> 
> ./configure -prefix /usr \
>              -docdir /usr/share/doc/qt \
>              -header.......
> 
> What do I need to do to fix the "bash" command?
> Thanks, Arden

 My best advice to you (at the risk of being called a grumpy old
man) is "learn to debug your scripts" ;-)

 In this case, apart from explaining the problem to somebody (or the
list, as you have done - and doing that *is* a valid debugging
process, so you are already on the way to succeeding), consider
where you are, and perhaps try running the command by hand.

 In this case, you appear to not be in the directory you think you
are - the configure script exists in the qt-long-name-3.3.7
directory when I untar it, and it is executable.  So, perhaps you
forgot to 'cd' (or perhaps you hardcoded the directory name
incorrectly, and didn't detect the failure to cd).

 The reason I mention running the command by hand is that qt asks
you to agree to the licence.  When you've read the text, it's no big
deal to use 'yes | ./configure ...', otherwise a script will hang
waiting for your response.

 However, I'm unclear why your script has the 'bash' line - doesn't
that just open up a shell until you key enter ?  If you are
scripting, make the script itself executable with #!/bin/sh or
#!/bin/bash if you are using bash-isms.  Invoking bash from within
a shell script is not an obviously correct thing to do - any results
other than an exit status will not be available to the calling
shell.  Yes, there are sometimes reasons to do it, but I suspect you
don't need it here.  Or do I misunderstand, and you think that by
passing some 'magic' to bash everything will be corrected ?

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to