stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Brown <mbr...@inbox.com>
Subject RE: Cygwin libc_decl.sh script error
Date Sat, 10 Mar 2007 18:05:22 GMT
> -----Original Message-----
> From: scottz@roguewave.com
> Sent: Fri, 9 Mar 2007 10:50:24 -0700
> To: stdcxx-dev@incubator.apache.org
> Subject: RE: Cygwin libc_decl.sh script error
> 
> Aha! That was the problem, difference between unix and windows line
> termination caused Cygwin to read in invalid character.  I had set
> Cygwin to read all files via binary.  I set Cygwin to read in DOS files
> and that solved the issue of script error.  I will continue to compile
> with gcc 4.1.1.

If you plan to work with the files under Cygwin downloading them in the
traditional UNIX format might make editing much easier. Otherwise some
editors might display control control characters for Windows newlines.
If I'm not mistaken, emacs likes to do that.

-- Mark

> 
> Yu (Scott) Zhong
> -----Original Message-----
> From: Farid Zaripov [mailto:Farid_Zaripov@epam.com]
> Sent: Friday, March 09, 2007 9:00 AM
> To: stdcxx-dev@incubator.apache.org
> Subject: RE: Cygwin libc_decl.sh script error
> 
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com]
>> Sent: Thursday, March 08, 2007 1:47 AM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: Re: Cygwin libc_decl.sh script error
>> 
>> Scott Zhong wrote:
>>> 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:
>> 
>> What's on your line 39? The line is empty in both 4.1.3 and
>> trunk which makes me suspect that either your local copy is
>> corrupted or your Cygwin installation may be broken or incomplete.
> 
>   The problem is in that the bash requires the script files in unix
> format,
> but this files have the dos format on windows.
> 
>   All you need is convert *.sh files to unix format using dos2unix
> utility.
> 
>   Changes are commited thus:
> http://svn.apache.org/viewvc?view=rev&rev=516404
> 
> Farid.

Mime
View raw message