Date: Thu, 22 Aug 2002 11:44:19 -0700 From: Skye Poier <skye@ffwd.cx> To: stable@freebsd.org Subject: Re: ports problems -- FIXED Message-ID: <20020822114419.G43401@ffwd.cx> In-Reply-To: <447kikn9ys.fsf@be-well.ilk.org>; from freebsd-stable-local@be-well.no-ip.com on Tue, Aug 20, 2002 at 11:53:47PM -0400 References: <AA62447DB04E5A4DB580858FD05C26E3026D3958@SNOEXC01.asiapacific.cpqcorp.net> <20020820094343.C62324@ffwd.cx> <20020820110208.I62324@ffwd.cx> <447kikn9ys.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is one of the things that really annoys me about the UNIX
"community". Why do you have to be a assh*le and blame me for a
completely non-intuitive mistake? Its not even a mistake really,
show me a man page or a handbook entry where it says "don't put trailing
slashes in your path".. and since I've been running it this way for
years, and haven't had any problems other than this libtool failure, I'd
say the problem lies in bsd.port.mk, not my .tcshrc
Sorry I'm not as 1337 as you, Lowell
Skye
Word on the street is Lowell Gilbert said:
> Skye Poier <skye@ffwd.cx> writes:
>
> > I found my problem.
> >
> > On like 2641 of bsd.port.mk:
> >
> > LIBTOOLDIR=`${WHICH} ${LIBTOOL} | ${SED} -e 's^/bin/libtool^/share/libtool^'` || ${LOCALBASE}/share/libtool; \
> >
> > However, my .tcshrc file contained set path = (... /usr/local/bin/ ...)
> > note the trailing slash.
> >
> > `which libtool` returned /usr/local/bin//libtool
> > which screwed up the sed substitution above.
> >
> > I think this should be fixed??? Probably by eliminating dup // in
> > tcsh's which command?
>
> Eliminating the extra slash in your path variable would be a more
> appropriate fix...
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020822114419.G43401>