Subject: Re: build.sh breakage?
To: Brian A. Seklecki <firstname.lastname@example.org>
From: Bill Stouder-Studenmund <email@example.com>
Date: 03/27/2007 09:31:02
Content-Type: text/plain; charset=us-ascii
On Sun, Mar 25, 2007 at 08:22:08PM +0100, David Laight wrote:
> On Sun, Mar 25, 2007 at 12:36:22PM -0500, Brian A. Seklecki wrote:
> > > /home/paul/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:\
> > > /usr/pkg/bin:/usr/pkg/sbin:/usr/games:/usr/local/bin: \
> > > /usr/local/sbin:.
> > I once had my life (well, life of my livelihood) threatened by a
> > very .....imposing (politically correct) female system administrator for
> > putting "." in my $PATH. =20
> > It not being present overrides one of the natural security mechanisms
> > present in UNIX-like environments.
> Actually it usually does no harm as the last item, and the scripts
> shouldn't barf at that.
The problem is that someone recently had build issue because the "mv"=20
which build.sh found (well one of the called make files) was for a target=
device and not for the host system. Thus builds failed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)
-----END PGP SIGNATURE-----