Re: [coLinux-users] Problems with cofs and .c Files : error: stray '\240'

[Henry N. <Henry.Ne@Arcor.de>]

Tiago Jost wrote:
> Hi.
> 
> First, sorry for my english. I´m working to make it better.
> Now,  my problem:
> I´m using coLinux to port a uClibC buildroot. It´s working fine, and i 
> can compile my arm9 programs just like I do in Suse 10, with the same 
> speed, if I copy all the files of my project  from windows partition 
> inside the environment, like /home/user/Project.
> 
> If I just mount the Windows partition, and try to compile the project 
> inside the mount point (like /mnt/win/c/Project), I got errors, on some 
> files, like:
> crypt.*c*:1350: *error*: *stray* '\240' in program
> 
> But the c file have just 1350 lines , for example, and the errors continue

The gcc internalny use 'mmap' to map your file into memory instead to 
read the file directly. Some times gcc reads behind the end of file, so 
you gets errors behid your last line of source file.

The bug results from 'fstab' on cofs device, that comes to fast after 
last write operation on the same file or directory.

I'm not remember, but there exist a parameter for gcc to disable the 
mapping source files into memory via 'mmap' and simple use only "open - 
read - close" for reading source files.

--
Henry