X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Does 'ar' work with native MS Windows libs? Date: Wed, 4 Oct 2006 12:52:08 -0400 Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F7B1377@PAUMAILU03.ags.agere.com> In-Reply-To: <4523C3CA.9070006@cygwin.com> From: "Williams, Gerald S \(Jerry\)" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k94GqXe7016503 Christopher Faylor wrote: > If 'ar' insists on backslash separators that is surely a bug. You may be right, but please stop calling me Shirley. :-) Larry Hall (Cygwin) wrote: > Why is that? If 'LIB.EXE' will work with either and 'ar' as a Cygwin > app prefers '/', why would working with a .lib produced by 'LIB.EXE' > containing '\' separators make 'ar' work better? Perhaps ar doesn't prefer either. It strips the directory name when you add files. It does tolerate directories in the form that LIB.EXE would normally generate (i.e., with backslashes). Yes, it is still arguably a bug if ar cannot handle files that LIB.EXE can produce, although there may be a reason. It's been a while since I looked into the internals of archive files, but I vaguely remember that slashes have a special meaning when found in archive directories. gsw -- 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/