delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
Message-ID: | <016c01c35143$aa3080f0$c15f893e@starfruit> |
From: | "Max Bowsher" <maxb AT ukf DOT net> |
To: | <cygwin AT cygwin DOT com> |
References: | <001301c350e2$695f2560$200aa8c0 AT thorin><17447438172 DOT 20030723171043 AT familiehaase DOT de> <16158 DOT 52061 DOT 186089 DOT 335053 AT phish DOT entomo DOT com> |
Subject: | Re: Questions about building from CVS (was Re: documentation on building the cygwin dll) |
Date: | Wed, 23 Jul 2003 18:55:51 +0100 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1165 |
David Rothenberger wrote: >> Gerrit P. Haase writes: >> > Try this: >> > >> > #!/bin/bash >> >> Gerrit, >> >> Thanks for the script! I just started building the cygwin DLL from >> sources last week and this script sure does make it easier. >> >> I do have two questions for those that have done it successfully. >> >> First, how do you do the update from CVS? If I go into the src >> directory (created from "cvs checkout winsup") and run "cvs update", >> I get a whole bunch of other packages in addition to winsup, which >> isn't right. If I run "cvs update" in "src/winsup", then the >> supporting files in src aren't updated. The best I can come up with >> is to do "cvs update -l && cvs update *" in the src directory. Is >> this how everyone else does it? Just don't use the -d option to update. >> Second, when I run make install (or your script), I find that it >> produces many errors related to directories not existing in the >> install directory. I generally have to create them by hand and then >> re-run "make install". I do the following: >> >> $ grep -h /bin/install: log.install* | \ >> sed 's/^.*`\([^'"'"']*\).*$/\1/' | \ >> xargs -n1 dirname | sort | uniq | \ >> xargs mkdir -p >> >> $ gerritsScript install >> >> Does everyone have this problem or is it something specific with my >> setup? It's a bug, see the cygwin-patches@ archive. Max. -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |