This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Config tool 2.04 parse error bug.
- To: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Subject: Re: [ECOS] Config tool 2.04 parse error bug.
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Mon, 13 Aug 2001 18:39:26 +0100
- Cc: 'Julian Smart' <julians at redhat dot com>,'eCos Disuss' <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <002201c12418$27e26cd0$090110ac@TRENT>
"Trenton D. Adams" wrote:
>
> I do have one more comment that I just thought of. I've noticed that
> the eCos docs say to "mount -f -b c: /c". I find that a lot of the time
> my code will not compile due to parse errors unless I "mount -f c: /c"
> for textmode.
Yes, that's likely the fix if you had /c mounted in binary mode before. If
you do "mount -f c: /c" does the problem go away? Where did you find
something that said to use -b?
I notice in the original problem it was using /cygdrive/C rather than
/cygdrive/c. I wonder if that's the difference. Can you try "mount -f c:
/C" just for amusement value?
> I have no idea why, but it might have something to do
> with the difference between linux/unix and windows carriage returns.
> eg. 0x0a 0x0d as opposed to 0x0a only. So, I would assume /cygdrive/c
> is binary mode by default!
It depends.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine