Re: Error building glibc-2.3.2 for my arm-9tdmi-linux cross compiler on cygwin

[Duane Ellis <duane at duaneellis dot com>]

J Johnson wrote:
> The problem seems to be in the generated build-glibc-headers/sysd-syscalls.  The line causing the problem seems to be related to the definition of "IFS" which spans two lines the last of which contains just a sinlge quote.  See a snip from the file below:
>
> ------------- BEGIN sysd-syscalls -----------------
>
> HOSTTYPE=i686
> IFS='  
> '
> JAVA_HOME='"C:\Program Files\Java\jdk1.5.0_13"'
>
> ---------------------- END --------------------------------
>
> Thoughts?
>   

I have *NOT* looked directly at that shipppit of script code in the 
original context.
While strange, the above is not uncommon. I believe, in effect, the IFS 
(input field separator) is a newline.
Having done *LOTS* of work with cygwin, a *VERY* common thing is the 
default End of Line.
When you installed cygwin, it asks... what to use. All scripts - like 
this *require* unix EOL.

Cygwin must know how to handle "\n" in IO operations.

Welcome to Unix Emulation, Enjoy the show :-)

at the cygwin bash$ prompt, type "mount" and see what it says:

In my case, it looks like this:

duane@desk ~
$ mount
C:\cygwin\bin on /usr/bin type system (binmode)
C:\cygwin\lib on /usr/lib type system (binmode)
C:\cygwin on / type system (binmode)
c: on /cygdrive/c type system (binmode,noumount)
e: on /cygdrive/e type system (binmode,noumount)

In my case, "binmode" is correct.

It is OK to use non-bin mode, if you are careful (ie: your own stuff)
But... it is *NOT* ok for things like 'autoconfig' scripts 
(configuration scripts and the ilk)

I personally gave up on CR/LF.


Also - you sometimes have problems with EDITORS.... converting, or 
inserting crud.

-Duane.



--
For unsubscribe information see http://sourceware.org/lists.html#faq