Message-ID: <BAY105-F133317E4A9528CB6ABB913D21F0@phx.gbl>
In-Reply-To: <452103B5.2080406@byu.net>
From: "Frank Illenseer" <franki2006 AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problems with archiver "ar"
Date: Mon, 02 Oct 2006 14:30:12 +0200
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

>Don't mount to /cygdrive/c/DATA/; mount points to a subdirectory of
>/cygdrive don't really do any good, because the path resolution does not
>look for mount points residing inside /cygdrive.  Instead, mount
>c:\data\myproject to a POSIX path (ie. something like /myProject).

Thanks, Eric, for pointing this out. - That clarifies all!


> > PS: The problem with "ar" is still there and I think (as Eric pointed
> > out) that "ar" is not correctly reading in binmode/textmode. Once I
> > solved the mounting problems, I will do some more tests with "ar".
>
>What more needs to be tested?  Until cgf releases a new binutils with an
>update to ar that forces binary mode on all archival actions, the current
>behavior on textmounts isn't going to change.

Thus I think the error seems to be clear and I need no further testing.
(I just wanted to narrow doewn, but you guys are rather familiar with the
source code and already know what is going wrong.)


Thanks! - And I am really looking forward to the next releases.



--
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/