-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 7 Aug 1998, Bryan Scaringe wrote:
>
> > I am trying to get this version of Pine installed. The docs say I need to
> > type "build help" to find out the 3 letter code for the platform I want to
> > compile on. But, build help only lists a code for Ultrix. Did I d/l the
> > wrong source code? The info on the Pine Tech notes web page gives the same
> > info as in the docs I have. Anyone have any ideas to get it installed? I
> > tried to install from a user account and then tried to install from root.
> > "build help" worked ok in the user account but not in root (bash: build:
> > command not found - even though I changed permissions to 777 & even tried
> > chown to root).
> >
>
> I am not familiar with build. However, if build is in the current
> directory, and the current directory is not in your path, you can
> not run it. Unlike dos, unix systems will not look in the current
> directory for a file. It only uses the PATH. In order to get around
> this, you can append "." to your PATH variable, to search whatever
> directory you are in. the superuser (root) should never have
> this in his/her path, as it invites security problems. However,
> normal users typically do. the workaround is to use "./build",
> rather than "build".
>
Thanks for the reply. I had already figured out that if it's not in the
path it won't work even if you're in the directory where the file resides.
I got Pine 4.02 installed last night.
And I figured out that lnx was the abbreviation that I needed to build
this version of Pine.
It would appear that some installation routines assume too much about
the installer. :)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQEVAwUBNct/aXTGIOlWZQ6lAQHYaAf/eqXVGPQNVq+FJgNr47btg9HwoN+wac1a
+tZkdbF1H9Ntfekvh3PSjcZGhAIAzJD6K+2BT5QCRwBMWaPNZ0EaQqBXytav36Lz
eeYWaaKVtaf31v6Fny6/34Pjm7pOgWizRGlhWreR5Oj58MAptHk1QI5j6djZG6yq
sy2uW52GFgkuKeT0PE6cRzYBctTKlI3Oqncd58dUH9LQiWAmZ3OEe8RZSRiUR7aT
SpStT7ug4tQUFX5ecobWVrYOVg3l8FYl8Yk9/aGwwtai6L+gAOdveG9jocw8BtCf
Kqf/lUbMoYZdLk4FLwLoCtDFODVHnf6JGN1DVnKQfWC/cCyRGClwZQ==
=Eqko
-----END PGP SIGNATURE-----
