From owner-freebsd-stable Thu Aug 22 14:37:17 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF88637B401 for ; Thu, 22 Aug 2002 14:37:08 -0700 (PDT) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0786643E4A for ; Thu, 22 Aug 2002 14:37:08 -0700 (PDT) (envelope-from freebsd-stable-local@be-well.no-ip.com) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.158]) by be-well.ilk.org (8.12.5/8.12.5) with ESMTP id g7MLb78u093850 for ; Thu, 22 Aug 2002 17:37:07 -0400 (EDT) (envelope-from freebsd-stable-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.5/8.12.5/Submit) id g7MLb7Et093847; Thu, 22 Aug 2002 17:37:07 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-stable-local@be-well.ilk.org using -f To: stable@freebsd.org Subject: Re: ports problems -- FIXED References: <20020820094343.C62324@ffwd.cx> <20020820110208.I62324@ffwd.cx> <447kikn9ys.fsf@be-well.ilk.org> <20020822114419.G43401@ffwd.cx> From: Lowell Gilbert Date: 22 Aug 2002 17:37:07 -0400 In-Reply-To: <20020822114419.G43401@ffwd.cx> Message-ID: <44fzx6fud8.fsf@be-well.ilk.org> Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Skye Poier writes: > Why do you have to be a assh*le and blame me for a > completely non-intuitive mistake? With all due respect, I did not express "blame" for anything. I indicated that solving the problem on your side rather than the system side was the best approach. You can argue with that (and you have -- in fact, you've partially convinced me) but taking my comment as an insult requires reading in a considerable amount of meaning that simply wasn't in my e-mail. > 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".. No, there aren't any such examples, and in most cases it *will* work fine. But nothing I can find says you *can* do it, either, and *all* of the examples leave out the trailing slashes. > 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 Changing the makefile is a very reasonable suggestion. (Adding a single '+' should fix problem you experienced, I think.) Your original suggestion, of changing csh to remove the slashes in the 'which' command output, is a relatively risky approach. Because csh is third-party software, making changes to it in the FreeBSD tree is something best avoided. Once again, I assure you my comments were not intended to be personal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message