RE: GDB-insight build errors

["Dave Korn" <dave dot korn at artimi dot com>]

On 03 August 2007 02:15, ariga masahiro wrote:

> Hi,
> 
> Concerning of the problem that cannot install insight6.6 properly.
> I think I discovered the most likely cause.
> Correct me if I wrong.
> 
> When I installed cygwin on Windows XP PC,
> I selected DOS format(CR-LF) files.
> Now don't you think that is the cause of entire problem?
> The reason is that my colleague tried to install insight6.6
> on his cygwin and succeeded and he installed cygwin in Unix format(LF)!

  Ah, yes, I'm sure that is the problem!

> Now let me explain why I installed in DOS format.
> I also at first installed in Unix format,but I encountered
> problems that shell can't read ecos batch files(ecosenv.sh etc.)
> like these,
> bash: $'\r': command not found
> ': not a valid identifierITORY
> bash: $'\r': command not found
> ': not a valid identifier
> bash: $'\r': command not found
> ': not a valid identifier
> I discovered files related to ecos configtool are all DOS formated.
> I don't know why.

  I think it was just because the ecos team decided to use windows-style line
ends for the convenience, since on windows, editors like notead and wordpad
use that format.  In the past, it did not matter, since older versions of
cygwin bash had compatibility enabled by default, and/or since ecos could just
specify that you must use text mode.  But nowadays this is a problem, since
bash no longer accepts incorrect line endings by default.  Your choices are:

- convert all ecos shell scripts using 'd2u'.
- set the igncr option in BASH_ENV, or by putting "set -o igncr" in your
.bashrc or similar, as described at
http://cygwin.com/ml/cygwin-announce/2007-05/msg00003.html

> Believe me I experienced terrible slough troubling by file format
> differences.
> So I determined to install cygwin and all in DOS format from the beginning.
> 
> Now it is the ultimate question if use DOS format or Unix format,
> as far as running under Windows.
> 
> I agree I should use Unix format on condition ecos configtool correctly
> output Unix format files.
> 
> I am all in ears what is your opinion.

  It is best to make use of the Unix format.  If the *only* thing you wanted
to use cygwin with was the ecos scripts, then you could use text mode and not
have to worry, but since you are going to wish to do non-ecos activities such
as building downloaded gnu tarballs, your life is much simpler if you run in
Unix mode.

  By the way, it is also *very important* that you use cygwin's command-line
tar utility to extract the files.  Do not use winzip, 7zip or any other GUI
tool, as they will not do the right thing about unix permissions, symlinks,
and other POSIX features that are supported by cygwin but not by native
windows apps.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....