bsetbg

Greg Turpin gregturp at home.com
Wed Oct 3 16:22:15 PDT 2001


Not having "which" is definitely your problem.

Taking a look at the bsetbg code - it tries a `which grep` and
if it returns an error it spits out that error message.

There is a hint for it on the LFS site.

Greg


On Wednesday 03 October 2001  4:09 pm, you wrote:
> On Thu, Oct 04, 2001 at 12:41:18AM +0200, Stefano wrote:
> > This is what i got after running bsetbg:
> >
> > bsetbg: error: couldn't find grep!
> > this script needs grep to be in your path in order to function.
> > you can get GNU grep from ftp://ftp.gnu.org/bin/gnu/grep/
> > root:/usr/local/blackbox-0.61.1$vi /usr/local/bin/bsetbg
> > root:/usr/local/blackbox-0.61.1$grep grep /usr/local/bin/bsetbg
> >    nogrep)
> >      echo "$NAME: error: couldn't find grep!"
> >      echo "this script needs grep to be in your path in order to
> > function." echo "you can get GNU grep from
> > ftp://ftp.gnu.org/bin/gnu/grep/" && exit 1 cat $TMPFILE | grep -v $APP >
> > $TMPFILE2
> > case `which grep 2>&1` in */*grep) : ;;
> >         error_msg nogrep
> >
> > Of course i have got grep in /usr/local/bin, so why this message?
> > Thanks,
>
> For starters, grep should be in /usr/bin, but as long as /usr/local/bin is
> in your $PATH it shouldn't be a disaster.
>
> The problem is that your package wants to run the 'which' program which
> doesn't exist on a normal LFS system. That would help towards it not being
> able to find grep, because bash will report that 'which' doens't exist.
>
> If which does exist, then check your $PATH to make sure it includes
> /usr/local/bin
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-support' in the subject header of the message



More information about the blfs-support mailing list