X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: updatedb broken [attn: lapack maintainer]
Date: Tue, 21 Mar 2006 22:18:30 +0000 (UTC)
Lines: 27
Message-ID:  <loom.20060321T231051-830@post.gmane.org>
References:  <44207423 DOT 6010602 AT elementcxi DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Steve Kelem <skelem <at> elementcxi.com> writes:

> 
> I'm having trouble running updatedb.  I've tried findutils-4.2.27-1 and 
> findutils-4.3.0-1.
> When I run updatedb manually, I get the message:
> updatedb needs to be able to execute /usr/lib/lapack/find, but cannot.
> The directory /usr/lib/lapack contains
> cygblas.dll   cyglapack.dll

That's because /etc/profile.d/lapack.sh is polluting the namespace with
BINDIR=/usr/lib/lapack, and then updatedb fails to use its default of
BINDIR=/usr/bin because BINDIR is already set.

I don't know if findutils or lapack is at fault for this conflicting
definition of what $BINDIR represents.  I can probably work around it
in the next findutils release, but wonder if the lapack maintainer should
instead be more careful to not pollute the environment during its profile.d
script.

In the meantime, as a workaround, you can do 'unset $BINDIR' prior
to running updatedb.

-- 
Eric Blake
volunteer cygwin findutils maintainer



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/