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 From: daniel DOT hempel AT philips DOT com Subject: Re: bug in "ar" when creating libraries on cross linked filesystems To: cygwin AT cygwin DOT com Message-ID: Date: Mon, 8 Sep 2003 15:18:22 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Hello, the output of "which ar" under cygwin is: ar is /usr/bin/ar ar is /bin/ar ... both are cygwin directories. The idea with "TMPDIR=. ar cq libdh.a a.o b.o" of Igor points in the right direction but it did not work ... maybe "rename" is not looking for the environment variable "TMPDIR". I still get the error message "ar: libdh.a: rename: Cross-device link" and the resulting library is empty. But as a workaround I changed the makefiles to create the library in "/tmp" and then I moved the result to ".": ar cq /tmp/libdh.a a.o b.o mv /tmp/libdh.a libdh. ... this is ugly but it works. Now I found out that also the program "ranlib.exe" has this renaming problem. I think that the "rename" command of libc is broken or "Services for Unix from Microsoft" is buggy. Maybe it is more successful to make the rename command in "libc" more robust than waiting for a bugfix from Microsoft ... Thanks for your ideas and help Daniel To: cygwin AT cygwin DOT com cc: (bcc: Daniel Hempel/HBR/RESEARCH/PHILIPS) Subject: Re: bug in "ar" when creating libraries on cross linked filesystems Ronald Landheer-Cieslak Classification: Sent by: cygwin-owner AT cygwin DOT com 05.09.2003 16:41 Please respond to cygwin I can't reproduce the problem and don't see anything out of the ordinary in your cygcheck output. Could you do a $ which ar and see if you're really working with Cygwin's ar? (I've just read Igor's reply - interesting hunch, but I'd have expected to be able to reproduce the problem..) rlc -- 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/