X-Spam-Check-By: sourceware.org Message-ID: <43A1D2C1.8D3CF8EA@dessent.net> Date: Thu, 15 Dec 2005 12:32:01 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Where is patch? References: <43A1A66B DOT 9080704 AT student DOT lu DOT se> <43A1A895 DOT A6231F0E AT dessent DOT net> <43A1ACF2 DOT 80600 AT student DOT lu DOT se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Lennart Borgman wrote: > I am not sure I understand what you mean. What is the "requires" line? It is in the setup.ini file (which is generated from the individual setup.hint files), which are not directly seen by the user but parsed by setup.exe. > Where is it? Should binutils have been dowloaded automatically when I > downloaded gcc-core? Yes, whenever you select a package for installation it should also select for installation all packages that that package requires. > When I look under Devel in setup.exe the binaries for binutils are > checked but without any download date. "which as" says "as" is not > found. Can you tell me what I should have done? Did I do something wrong > or is there perhaps a bug? Could it perhaps be because the downloader > stalled? (Maybe because of slow download here.) Ah, that might explain it. Setup is not all that great about error recovery. Fortunately you can work around this by just running it again if anything abnormal happens. Every time you run setup it will first add any packages that are not installed but listed as a requirement by packages that are installed. So if you just run it, and don't select anything, then you should get any missing dependencies downloaded and installed. Brian -- 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/