Scott Zhong wrote:
I tried wiping the Cygwin directory clean and reinstalling.  The problem
still persists.  I even compiled the newest GNU BASH shell.  I'm running
a lot of Windows applications on my laptop, could be the cause of BASH
script failure.  I think Cygwin is telling me to stick with MSVC ;)

Bite your tongue! ;-)

Hopefully Farid's suggestion to run dos2unix or his patch will
fix it for you. If not, let us know!

Martin


Yu (Scott) Zhong

-----Original Message-----
From: Mark Brown [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 7:13 PM
To: [email protected]; [email protected]
Subject: RE: Cygwin libc_decl.sh script error

I have not tried gcc 4.1.1 on Cygwin yet but I successfully configured
stdcxx/trunk with gcc 3.4.4. Aside from the problems I reported I also
got it to build in at least one configuration. I have not seen the
problem you pointed out.

-- Mark


-----Original Message-----
From: [EMAIL PROTECTED]
Sent: Wed, 7 Mar 2007 16:11:56 -0700
To: [email protected]
Subject: Cygwin libc_decl.sh script error

Windows XP with Cygwin DLL 1.5.24-2

GNU GCC 4.1.1



checking if the compiler is sane                   ok (invoked with
gcc)
checking if the linker is sane                     ok (invoked with
gcc)
checking system architecture                       ILP32 little endian

: command not found/stdcxx/etc/config/src/libc_decl.sh: line 39:

: command not found/stdcxx/etc/config/src/libc_decl.sh: line 42:

: command not found/stdcxx/etc/config/src/libc_decl.sh: line 44:

/cygdrive/c/csports/stdcxx/etc/config/src/libc_decl.sh: line 103:
syntax
error near unexpected t

'ken `do

'cygdrive/c/csports/stdcxx/etc/config/src/libc_decl.sh: line 103: `for
h
in $hdrs ; do



checking for overloads of abs()                    ok

checking for atomic operations                     ok

checking for bad_alloc assignment operator              11 [sig]
GLOBAL_BAD_EXCEPTION 3684 C:\cy

gwin\build\stdcxx\include\GLOBAL_BAD_EXCEPTION.exe: *** fatal error -
called with threadlist_ix

-1



Yu (Scott) Zhong

Reply via email to