Re: problem with egrep and fgrep

[Ralph Corderoy]

Hi Bob,

> > That doesn't ring true.  Certainly, after `make install', it isn't
> > expected that a package will work other than where it has been
> > installed, unless something like GNU Stow is used to patch things
> > up, so there seems little reason why the egrep script can't hardcode
> > grep's location.
> 
> I often use tools installed on an NFS server on an NFS client.  Others
> use tools on AFS clients where the install path is not the same as the
> usage path.

So how do you cope with programs that need to know where to find
run-time resources at compile time, e.g. perl.

    $ perl -V
    Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration:
    ...
      @INC:
        /usr/lib/perl5/5.6.1/i386-linux
        /usr/lib/perl5/5.6.1
        /usr/lib/perl5/site_perl/5.6.1/i386-linux
        /usr/lib/perl5/site_perl/5.6.1
        /usr/lib/perl5/site_perl/5.6.0/i386-linux
        /usr/lib/perl5/site_perl/5.6.0
        /usr/lib/perl5/site_perl
        .

Cheers,

-- 
Ralph Corderoy.      http://inputplus.co.uk/ralph/     http://troff.org/