RE: gdb and older cygwins

[Fabian Cenedese <Cenedese@indel.ch>]

>> > [Did I guess correctly how you managed to get your gcc 
>> sources mangled?]
>> 
>> It depends. I use cygwin only to compile gcc/gdb+co. The 
>> intended platform
>> to use them is Windows with cygwin.dll, not the whole Cygwin 
>> system. So
>> the source files which gcc will need to cope with ARE Windows 
>> text files.
>
>  You have two misunderstandings here:
>
>#1.  The cygwin dll is all you need to be using Cygwin; it's the dll that
>provides the posix environment, it's the dll that handles
>textmode-vs-binmode and line endian-ness issues.  Windows-plus-cygwin-dll
>equals cygwin equals Unix style line-ends.

In this case I meant with cygwin system the bash, the shell. I will not use
them on the cygwin shell but on windows even if that doesn't make a
difference.
"cygwin equals Unix style line-ends", so why can you set the style upon
installing cygwin?

>#2.  It doesn't matter what platform you want to compile on.  The gcc
>sources come with Unix-style LF line ends.  They are NOT Windows text files
>unless *you* have altered them.  If they now have CRs in them, it was *you*
>who put them there, when you didn't need to do so, and if you hadn't done
>so, it would have compiled fine under 2.95.3

I think that's something you missunderstood since the first mail. I have no
problems with the gcc/gdb sources, they are unpacked as they should be,
they still have LF endings, I can compile all (except other problems). It's
the resulting gcc which needs to eat CRLF endings (and gives me problems).
But that should be solvable with one of the six possibilities Michael gave me.

>  It didn't understand bzip2 last time I checked, but it had no trouble
>whatsoever with either tar, gz, or .tar.gz.  In fact some versions (v8
>upward IIRC) even have an option to decide whether to mangle line-ends or
>not specifically when unpacking a tar file.

Too unreliable. I ran into problems too many times like that, be it cygwin
and windows or linux and windows. If I need the sources on a certain
system I also unpack it there with the accompanying tools.

>> As I will use gcc and gdb from Windows (and not in Cygwin) I guess
>> this is no option for me.
>
>  As I point out above, if the cygwin dll is involved, you *are* in Cygwin;
>what you are running is *not* a native windows app and will follow Cygwin's
>preferences for line-end style.

I meant the mounting. Windows already has its drives, there will be no
mounting. It just has to work as delivered. Even worse at the customers'.
We don't know what drives they will have and use, so we can't mount
anything for cygwin.

But I think we're getting OT here :)

Thanks

bye  Fabi