RE: Error building GCC for ARM-elf on Cygwin 1.1.6

RE: Error building GCC for ARM-elf on Cygwin 1.1.6

[David Korn]

>-----Original Message-----
>From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
>Sent: 05 January 2001 18:37

>The copying will just copy the files verbatim, without translation. So if
>your headers in the source directory contain CRLFs, then being on a
>textmode mount won't help when they are copied.

>So as you suggest, doing CRLF->LF conversion on the headers in the source
>directory would probably fix this.

  Mmm.  Alas, I checked over the weekend, and it turns out the copies
in sys-include have been properly converted; I must have already done it
manually.  So somehow they're getting converted back by fixincs, which is
odd, since it's all shell scripts and sed.  Have you got any other ideas?

       DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Error building GCC for ARM-elf on Cygwin 1.1.6

[Jonathan Larmour]

David Korn wrote:
> 
> >-----Original Message-----
> >From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
> >Sent: 05 January 2001 18:37
> 
> >The copying will just copy the files verbatim, without translation. So if
> >your headers in the source directory contain CRLFs, then being on a
> >textmode mount won't help when they are copied.
> 
> >So as you suggest, doing CRLF->LF conversion on the headers in the source
> >directory would probably fix this.
> 
>   Mmm.  Alas, I checked over the weekend, and it turns out the copies
> in sys-include have been properly converted; I must have already done it
> manually.  So somehow they're getting converted back by fixincs, which is
> odd, since it's all shell scripts and sed.  Have you got any other ideas?

The only things I can suggest is to make sure /tmp is mounted in binary
mode. And also mount the directory somewhere else in binary mode. Just
because it's on a text-mode mounted directory now doesn't mean you can't
remount it in binary mode as well somewhere else.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Error building GCC for ARM-elf on Cygwin 1.1.6

[Jonathan Larmour]

David Korn wrote:
> 
> >-----Original Message-----
> >From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
> >Sent: 05 January 2001 18:37
> 
> >The copying will just copy the files verbatim, without translation. So if
> >your headers in the source directory contain CRLFs, then being on a
> >textmode mount won't help when they are copied.
> 
> >So as you suggest, doing CRLF->LF conversion on the headers in the source
> >directory would probably fix this.
> 
>   Mmm.  Alas, I checked over the weekend, and it turns out the copies
> in sys-include have been properly converted; I must have already done it
> manually.  So somehow they're getting converted back by fixincs, which is
> odd, since it's all shell scripts and sed.  Have you got any other ideas?

The only things I can suggest is to make sure /tmp is mounted in binary
mode. And also mount the directory somewhere else in binary mode. Just
because it's on a text-mode mounted directory now doesn't mean you can't
remount it in binary mode as well somewhere else.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: Error building GCC for ARM-elf on Cygwin 1.1.6

[David Korn]

>-----Original Message-----
>From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
>Sent: 05 January 2001 18:37

>The copying will just copy the files verbatim, without translation. So if
>your headers in the source directory contain CRLFs, then being on a
>textmode mount won't help when they are copied.

>So as you suggest, doing CRLF->LF conversion on the headers in the source
>directory would probably fix this.

  Mmm.  Alas, I checked over the weekend, and it turns out the copies
in sys-include have been properly converted; I must have already done it
manually.  So somehow they're getting converted back by fixincs, which is
odd, since it's all shell scripts and sed.  Have you got any other ideas?

       DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: Error building GCC for ARM-elf on Cygwin 1.1.6

[David Korn]

   Hi there,

>> The build failed with the following error:

>> _muldi3
>> In file included from /src/gcc/gcc-2.95.
>> include/stddef.h:1: Invalid token in exp
>
>I can't be entirely sure since I haven't come across this before, but it
>may be a problem with CRLFs. What happens when you type "mount" at a cygwin
>bash prompt? Did you unpack the sources in the way the web page said?

   I get this all the time too.  I don't know why, since my target headers
lives on a textmode mount, and my build directory is mounted binary; I 
guess the configure process copies them (from the directory indicated by
--with-headers= to the $prefix/$target/sys-include directory) in binary
mode in a way that bypasses the CRLF translation somehow.  Anyway, what
I do when I see this is 

  pushd gcc/include 
  find . -name \*.h -ls -exec dos2unix \{\} \;
  popd

and carry on with the build.  dos2unix is a shell script in /bin that says:

  #!/bin/sh
  tr -d '\015'

  Perhaps if I tried the find command in my sys-include directory that would
fix it, but I haven't been that bothered by it.

     hth,
        DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Error building GCC for ARM-elf on Cygwin 1.1.6

[Jonathan Larmour]

David Korn wrote:
> 
>    Hi there,
> 
> >> The build failed with the following error:
> 
> >> _muldi3
> >> In file included from /src/gcc/gcc-2.95.
> >> include/stddef.h:1: Invalid token in exp
> >
> >I can't be entirely sure since I haven't come across this before, but it
> >may be a problem with CRLFs. What happens when you type "mount" at a cygwin
> >bash prompt? Did you unpack the sources in the way the web page said?
> 
>    I get this all the time too.  I don't know why, since my target headers
> lives on a textmode mount, and my build directory is mounted binary; I
> guess the configure process copies them (from the directory indicated by
> --with-headers= to the $prefix/$target/sys-include directory) in binary
> mode in a way that bypasses the CRLF translation somehow.

The copying will just copy the files verbatim, without translation. So if
your headers in the source directory contain CRLFs, then being on a
textmode mount won't help when they are copied.

So as you suggest, doing CRLF->LF conversion on the headers in the source
directory would probably fix this.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Error building GCC for ARM-elf on Cygwin 1.1.6

[Renato Levy]

I have followed the instructions on
http://sources.redhat.com/ecos/tools/win-arm-elf.html as close as I could
and everything went fine, until I tryied to build Gcc

(I'm running WINNT)

The build failed with the following error:

  /tmp/build/gcc/gcc/xgcc -B/tmp/build/g
f/bin/ -I/tools/H-i686-pc-cygwin/arm-elf
   -g -O2 -I./include  -Dinhibit_libc  -
D -Dinhibit_libc   -I. -I/src/gcc/gcc-2.
g -I/src/gcc/gcc-2.95.2/gcc/../include -
       /src/gcc/gcc-2.95.2/gcc/libgcc2.c
  if [ $? -eq 0 ] ; then true; else exit
  arm-elf-ar rc tmplibgcc2.a ${name}.o;
  rm -f ${name}.o; \
done
_muldi3
In file included from /src/gcc/gcc-2.95.
include/stddef.h:1: Invalid token in exp
make[3]: *** [libgcc2.a] Error 1
make[3]: Leaving directory `/tmp/build/g
make[2]: *** [stmp-multilib-sub] Error 2
make[2]: Leaving directory `/tmp/build/g
make[1]: *** [stmp-multilib] Error 1
make[1]: Leaving directory `/tmp/build/g
make: *** [all-gcc] Error 2
make: Leaving directory `/tmp/build/gcc'

What have I done wrong. I've done once and again with the same error.


Renato Levy
Systems Analyst
Intelligent Automation, Inc.
7519 Standish Place, ste 200
Rockville, MD 20855
phone: (301)590-3155
fax: (301) 590-9414
WWW: http://www.i-a-i.com



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: Error building GCC for ARM-elf on Cygwin 1.1.6

[David Korn]

>-----Original Message-----
>From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
>Sent: 08 January 2001 11:44


>The only things I can suggest is to make sure /tmp is mounted in binary
>mode. And also mount the directory somewhere else in binary mode. Just
>because it's on a text-mode mounted directory now doesn't mean you can't
>remount it in binary mode as well somewhere else.

  My mounts are:-

-NT-                -POSIX-   -Type-  -Flags-
C:\cygwin\mnt\dos   /dos      system  textmode
C:\cygwin\bin       /usr/bin  system  binmode
C:\cygwin\lib       /usr/lib  system  binmode
d:\download         /download user    binmode
C:\Source           /dev2     user    textmode
C:\cygwin           /         system  binmode
C:\CVS4             /gccdev   user    textmode
G:                  /zip0     system  binmode
c:                  /win/c    system  textmode
d:                  /win/d    system  textmode
e:                  /win/e    system  textmode

  And my target headers live on C:\Tornado\target\h.  So I do configure
--with-headers=/win/c/Tornado/target/h; the configure process copies them
to /usr/local/sys-include, and I have to convert them manually.

  Then I go to build it.  At this stage, my source dir is /gccdev, which is
a textmode mount in order to avoid any problems with EOLs in the source
code, and my build directory is under ~, which is in /home, which is binary
mode.  And my tmp dir is the same.  Now, AFAIUI, nothing should be written
to or from my source directory when I've configure to build in a different
object directory, which is the only obvious way I can see of the LFs getting
converted back to CRLFs. So it's a mystery to me.

  Cheers for your suggestions, anyway.

        DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Error building GCC for ARM-elf on Cygwin 1.1.6

[Jonathan Larmour]

Renato Levy wrote:
> 
> I have followed the instructions on
> http://sources.redhat.com/ecos/tools/win-arm-elf.html as close as I could
> and everything went fine, until I tryied to build Gcc
> 
> (I'm running WINNT)
> 
> The build failed with the following error:
> 
>   /tmp/build/gcc/gcc/xgcc -B/tmp/build/g
> f/bin/ -I/tools/H-i686-pc-cygwin/arm-elf
>    -g -O2 -I./include  -Dinhibit_libc  -
> D -Dinhibit_libc   -I. -I/src/gcc/gcc-2.
> g -I/src/gcc/gcc-2.95.2/gcc/../include -
>        /src/gcc/gcc-2.95.2/gcc/libgcc2.c
>   if [ $? -eq 0 ] ; then true; else exit
>   arm-elf-ar rc tmplibgcc2.a ${name}.o;
>   rm -f ${name}.o; \
> done
> _muldi3
> In file included from /src/gcc/gcc-2.95.
> include/stddef.h:1: Invalid token in exp

I can't be entirely sure since I haven't come across this before, but it
may be a problem with CRLFs. What happens when you type "mount" at a cygwin
bash prompt? Did you unpack the sources in the way the web page said?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: Error building GCC for ARM-elf on Cygwin 1.1.6

[David Korn]

>-----Original Message-----
>From: Jonathan Larmour [ mailto:jlarmour@redhat.com ]
>Sent: 08 January 2001 11:44


>The only things I can suggest is to make sure /tmp is mounted in binary
>mode. And also mount the directory somewhere else in binary mode. Just
>because it's on a text-mode mounted directory now doesn't mean you can't
>remount it in binary mode as well somewhere else.

  My mounts are:-

-NT-                -POSIX-   -Type-  -Flags-
C:\cygwin\mnt\dos   /dos      system  textmode
C:\cygwin\bin       /usr/bin  system  binmode
C:\cygwin\lib       /usr/lib  system  binmode
d:\download         /download user    binmode
C:\Source           /dev2     user    textmode
C:\cygwin           /         system  binmode
C:\CVS4             /gccdev   user    textmode
G:                  /zip0     system  binmode
c:                  /win/c    system  textmode
d:                  /win/d    system  textmode
e:                  /win/e    system  textmode

  And my target headers live on C:\Tornado\target\h.  So I do configure
--with-headers=/win/c/Tornado/target/h; the configure process copies them
to /usr/local/sys-include, and I have to convert them manually.

  Then I go to build it.  At this stage, my source dir is /gccdev, which is
a textmode mount in order to avoid any problems with EOLs in the source
code, and my build directory is under ~, which is in /home, which is binary
mode.  And my tmp dir is the same.  Now, AFAIUI, nothing should be written
to or from my source directory when I've configure to build in a different
object directory, which is the only obvious way I can see of the LFs getting
converted back to CRLFs. So it's a mystery to me.

  Cheers for your suggestions, anyway.

        DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Error building GCC for ARM-elf on Cygwin 1.1.6

[Jonathan Larmour]

David Korn wrote:
> 
>    Hi there,
> 
> >> The build failed with the following error:
> 
> >> _muldi3
> >> In file included from /src/gcc/gcc-2.95.
> >> include/stddef.h:1: Invalid token in exp
> >
> >I can't be entirely sure since I haven't come across this before, but it
> >may be a problem with CRLFs. What happens when you type "mount" at a cygwin
> >bash prompt? Did you unpack the sources in the way the web page said?
> 
>    I get this all the time too.  I don't know why, since my target headers
> lives on a textmode mount, and my build directory is mounted binary; I
> guess the configure process copies them (from the directory indicated by
> --with-headers= to the $prefix/$target/sys-include directory) in binary
> mode in a way that bypasses the CRLF translation somehow.

The copying will just copy the files verbatim, without translation. So if
your headers in the source directory contain CRLFs, then being on a
textmode mount won't help when they are copied.

So as you suggest, doing CRLF->LF conversion on the headers in the source
directory would probably fix this.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

RE: Error building GCC for ARM-elf on Cygwin 1.1.6

[David Korn]

   Hi there,

>> The build failed with the following error:

>> _muldi3
>> In file included from /src/gcc/gcc-2.95.
>> include/stddef.h:1: Invalid token in exp
>
>I can't be entirely sure since I haven't come across this before, but it
>may be a problem with CRLFs. What happens when you type "mount" at a cygwin
>bash prompt? Did you unpack the sources in the way the web page said?

   I get this all the time too.  I don't know why, since my target headers
lives on a textmode mount, and my build directory is mounted binary; I 
guess the configure process copies them (from the directory indicated by
--with-headers= to the $prefix/$target/sys-include directory) in binary
mode in a way that bypasses the CRLF translation somehow.  Anyway, what
I do when I see this is 

  pushd gcc/include 
  find . -name \*.h -ls -exec dos2unix \{\} \;
  popd

and carry on with the build.  dos2unix is a shell script in /bin that says:

  #!/bin/sh
  tr -d '\015'

  Perhaps if I tried the find command in my sys-include directory that would
fix it, but I haven't been that bothered by it.

     hth,
        DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Re: Error building GCC for ARM-elf on Cygwin 1.1.6

[Jonathan Larmour]

Renato Levy wrote:
> 
> I have followed the instructions on
> http://sources.redhat.com/ecos/tools/win-arm-elf.html as close as I could
> and everything went fine, until I tryied to build Gcc
> 
> (I'm running WINNT)
> 
> The build failed with the following error:
> 
>   /tmp/build/gcc/gcc/xgcc -B/tmp/build/g
> f/bin/ -I/tools/H-i686-pc-cygwin/arm-elf
>    -g -O2 -I./include  -Dinhibit_libc  -
> D -Dinhibit_libc   -I. -I/src/gcc/gcc-2.
> g -I/src/gcc/gcc-2.95.2/gcc/../include -
>        /src/gcc/gcc-2.95.2/gcc/libgcc2.c
>   if [ $? -eq 0 ] ; then true; else exit
>   arm-elf-ar rc tmplibgcc2.a ${name}.o;
>   rm -f ${name}.o; \
> done
> _muldi3
> In file included from /src/gcc/gcc-2.95.
> include/stddef.h:1: Invalid token in exp

I can't be entirely sure since I haven't come across this before, but it
may be a problem with CRLFs. What happens when you type "mount" at a cygwin
bash prompt? Did you unpack the sources in the way the web page said?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Error building GCC for ARM-elf on Cygwin 1.1.6

[Renato Levy]

I have followed the instructions on
http://sources.redhat.com/ecos/tools/win-arm-elf.html as close as I could
and everything went fine, until I tryied to build Gcc

(I'm running WINNT)

The build failed with the following error:

  /tmp/build/gcc/gcc/xgcc -B/tmp/build/g
f/bin/ -I/tools/H-i686-pc-cygwin/arm-elf
   -g -O2 -I./include  -Dinhibit_libc  -
D -Dinhibit_libc   -I. -I/src/gcc/gcc-2.
g -I/src/gcc/gcc-2.95.2/gcc/../include -
       /src/gcc/gcc-2.95.2/gcc/libgcc2.c
  if [ $? -eq 0 ] ; then true; else exit
  arm-elf-ar rc tmplibgcc2.a ${name}.o;
  rm -f ${name}.o; \
done
_muldi3
In file included from /src/gcc/gcc-2.95.
include/stddef.h:1: Invalid token in exp
make[3]: *** [libgcc2.a] Error 1
make[3]: Leaving directory `/tmp/build/g
make[2]: *** [stmp-multilib-sub] Error 2
make[2]: Leaving directory `/tmp/build/g
make[1]: *** [stmp-multilib] Error 1
make[1]: Leaving directory `/tmp/build/g
make: *** [all-gcc] Error 2
make: Leaving directory `/tmp/build/gcc'

What have I done wrong. I've done once and again with the same error.


Renato Levy
Systems Analyst
Intelligent Automation, Inc.
7519 Standish Place, ste 200
Rockville, MD 20855
phone: (301)590-3155
fax: (301) 590-9414
WWW: http://www.i-a-i.com



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com