X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=D8KSnuiRTCU243byIFZonca8czMOS MKmOFFl2lP+V/CM4MwSQw4qvkJ18TNX7pUCASaeVFwdzs/njFqkEBI/LQcjKUsBO z9onCWfDUcLvc/SBGS8DqcJHUMUqBtHodANKXKqap8LBA+LKhYpAOVD923BabTyA tr508MyCNJB7Lg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=C+krcuoSJdgkN4wCk+aP7PO0Jz0=; b=AWP rt+Oc4o+l/wyLCIeV5BJxjR5CuzkhATK08mc8jpegKPVEBrt7325b6zfi8fKW7wd vbj1d7FXQ142lbRPvp3w5mXHqnHrdHWPxmZHXeuaeZYe7EDlKYlyMGWwLrHnZsCx ctw2YEG7kzUHmQcz7BiXjiIACpdsc1ofEMp825kA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2 MIME-Version: 1.0 X-Received: by 10.59.8.232 with SMTP id dn8mr9704636ved.8.1376487807854; Wed, 14 Aug 2013 06:43:27 -0700 (PDT) Date: Wed, 14 Aug 2013 09:43:27 -0400 Message-ID: Subject: 64-bit Cygwin installation is missing /usr/bin/lockfile From: Steve Rowley To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 > On 8/13/2013 6:49 PM, Christopher Faylor wrote: >> On Tue, Aug 13, 2013 at 05:29:46PM -0400, Larry Hall (Cygwin) wrote: >>> On 8/13/2013 5:01 PM, Steve Rowley wrote: >>> I just installed 64-bit Cygwin on Win7, and noticed that >>> /usr/bin/lockfile is missing in my installation. >>> >> As always, you can find what package something is in by searching for it >> here: >> >> In the case of lockfile, you can see the results here: >> >> >> However note that, currently, this only searches the 32-bit version of >> Cygwin. Some packages are still missing from the 64-bit version. > > The fact that some packages don't exist yet for 64-bit is something > that does deserve highlighting. Of course, whether or not the package > actually exists for 64-bit, the package search will tell you if it > exists in the 32-bit world, so at least one knows what to look for. > In this particular case, I did go looking to see if 'procmail' was > already available for 64-bit. As it turns out, it is. Thank you for for the pointer to how to find the Cygwin package containing a file; that is indeed a useful thing to know. Since procmail is the home of /usr/bin/lockfile, I reinstalled procmail. However, /usr/bin/lockfile is still missing. Unpacking the procmail 3.22-12 tarball reveals that it contains only the /usr/share/doc/procmail/ directory, and 4 small documentation files. The rest of procmail is missing. If this is something that will take a while, then perhaps I should go back to the 32-bit installation so my scripts will work while waiting for a fix. But as uninstalling and reinstalling a rather large Cygwin installation is painful, I'd rather not do this if lockfile will be available in a week or so. Does anyone have advice as to whether it's worth waiting vs going back to 32 bit? Tnx. ___________ Steve Rowley http://alum.mit.edu/www/sgr/ Skype: sgr000 It is very dark & after 2000. If you continue, you are likely to be eaten by a bleen. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple