Re: Problems with archiver "ar"

2006-10-02 Thread Frank Illenseer
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 point

Re: Problems with archiver "ar"

2006-10-02 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Frank Illenseer on 10/2/2006 2:51 AM: > >C:\DATA\myProject\solution1 > > so I tried (taking your mount as reference) > > mount -f -u -t "C:\DATA\myProject\solution1" > "/cygdrive/c/DATA/myProject/solution1" Don't mount to /cygdri

Re: Problems with archiver "ar"

2006-10-02 Thread Frank Illenseer
Thanks Eric for the proposals for "mount": >mount -f -u -t "c:/cygwin/home/eblake/text" "/home/eblake/text" Unfortunately this does not work for me. (Shell scripts still show that this is not mounted in textmode). The directory I have to mount in textmode would be C:\DATA\myProject\solu

Re: Problems with archiver "ar"

2006-09-28 Thread Igor Peshansky
On Thu, 28 Sep 2006, Eric Blake wrote: > According to Frank Illenseer on 9/28/2006 5:34 AM: > > > $ which sh > > /usr/bin/sh > > > > $ ll /usr/bin/sh > > lrwxrwxrwx 1 illenseer Kein 8 Jul 20 2005 /usr/bin/sh -> bash.exe > > While cygwin doesn't mind a symlink, they won't work if you try to use >

Re: Problems with archiver "ar"

2006-09-28 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Frank Illenseer on 9/28/2006 5:34 AM: >> Sounds like ar needs to be taught about open(O_BINARY)/fopen("rb") (or be >> linked with binmode.o). > > Do I have to post this advice in any other list to get it to note to the > correct persons?

Re: Problems with archiver "ar"

2006-09-28 Thread Frank Illenseer
[Sending this to the mailing list also, as my reply only got to eric directly...] Hi Eric, first of all thanks for your reply. Sounds like ar needs to be taught about open(O_BINARY)/fopen("rb") (or be linked with binmode.o). Do I have to post this advice in any other list to get it to note

RE: Problems with archiver "ar"

2006-09-27 Thread Gary R. Van Sickle
> From: Eric Blake > Sent: Wednesday, September 27, 2006 8:42 PM > Subject: Re: Problems with archiver "ar" > [snip] > > > > But due to the newest bash update, I rather need "textmode" > to re-use > > my existing scripts without conversion,

Re: Problems with archiver "ar"

2006-09-27 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Frank Illenseer on 9/27/2006 11:34 AM: > Sorry - for not providing all infos... > > I did some additional tests: When mounting my drives in "binmode" the > error is gone and when mounting them in "textmode" the error is there. Sounds lik

Re: Re: Problems with archiver "ar"

2006-09-27 Thread Frank Illenseer
Sorry - for not providing all infos... I did some additional tests: When mounting my drives in "binmode" the error is gone and when mounting them in "textmode" the error is there. But due to the newest bash update, I rather need "textmode" to re-use my existing scripts without conversion, as

Problems with archiver "ar"

2006-09-26 Thread Frank Illenseer
Hi all, with the current CYGWIN installation I suddenly get errors with the archiver "ar": ar: creating MYlib.a 15 [main] ar 3024 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) or ar: MYlib.a: Memory exhausted I am using CYGWIN on Windows X

Re: Problems with archiver "ar"

2006-09-26 Thread Christopher Faylor
On Tue, Sep 26, 2006 at 05:00:57PM +0200, Frank Illenseer wrote: >with the current CYGWIN installation I suddenly get errors with the >archiver "ar": > > ar: creating MYlib.a > 15 [main] ar 3024 _cygtls::handle_exceptions: Error while dumping >state > (probably corrupted stack) > >or >