From: Tiago J. <tia...@ya...> - 2007-07-05 00:58:40
|
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 crypt.*c*:1351: *error*: *stray* '\130' in program I think that it was a problem with encode type or line delimiters, then I compare the files with error and the files without error in a hex edit, and both are ok. Then, I start a new file with code, and compile it every 100 lines. It goes ok in the first 3 times, and when the program was with ~400 lines, the same errors occurs again. I compare the files in my project, and in fact, this only happens in files with more than 400 lines (I don´t know the file size, I will check it, think that the size is the problem). I test with coLinux+ArchLinux and andLinux. To "solve" my problem, I now mount the Windows hd with smbmount, and the error don´t occur. My windows filesystem is NTFS, and I try the same with a PenDrive Does anybody have a similar problem and can help-me? Thanks. Tiago Jost _______________________________________________________ Yahoo! Mail - Sempre a melhor opção para você! Experimente já e veja as novidades. http://br.yahoo.com/mailbeta/tudonovo/ |