X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Lewis Hyatt Subject: Re: Problem compiling cygwin-1.5.24-2 Date: Tue, 05 Jun 2007 17:27:19 -0400 Lines: 24 Message-ID: References: <7828.51888002387$1181078494@news.gmane.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) In-Reply-To: <7828.51888002387$1181078494@news.gmane.org> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Olivier Langlois wrote: > Hi, > > I kinda isolated the weird file access problem. The corruption seems to come > from the setup.exe program as if I download manually > cygwin-1.5.24-2-src.tar.bz2, unzip and untar it manually, the permissions > for all files are ok. > > Greetings, > Olivier Langlois > http://www.streamtheworld.com > > > "Corruption" isn't quite accurate. When you download source files, setup.exe puts them in /usr/src, which is a managed mount, to insure that Windows-incompatible file names can still be preserved. If you copy files from /usr/src outside of cygwin, then the filenames will become mangled. If you use cygwin's cp to copy them, then there should be no problems unless some of the filenames are not legal Windows filenames. That's probably what was happening here. -Lewis -- 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/