RE: [DotGNU]cscc problems in migration to ARM

[Dawkins, David]

> -----Original Message-----
> From: imateos [mailto:address@hidden
> Sent: 30 April 2003 13:12
> To: Dawkins, David
> Cc: address@hidden
> Subject: Re: [DotGNU]cscc problems in migration to ARM
> 
> 
> Dawkins, David wrote:
> 
> >One fix I had to make was to make sure that fopen() included the 
> >"b" flag (binary) for x86 platforms, to stop carriage-return/linefeed
> >translation. This got checked in, but it may have been conditionally
> >compiled for platform.
> >
> >I forget where it was, but some grepping should find it.
> >
> >Is ARM one of those cases? 

> >> [......]

> >>When I try to compile (with cscc) I obtain the next error:
> >>
> >>metadata error in token 0x00000001: bad string index
> >>
> >>/home/imateos/hello2.objtmp: invalid metadata in image
> >>
> >>/home/imateos/hello2.exe: no entry point specified
> >>
> >>Does anyone knows what's going wrong?
> >>
> >>Thanks in advance.
> >>
> >>Ignasi
>
> >
> I've been unable to find where fopen( ) is checked for the "b" flag.
> Anyway, I don't understand how this would affect cscc when trying to 
> compile a  .cs file.
> As far as I understand, this error is  generated when trying 
> to parse an 
> index of the metadata. Is this correct? or I'm terribly lost?

I just looked and it seems that we use "rb" unconditionally, so I'm
just confusing things for you.

My suspicion was that something during the compile/link phase was
reading in binary data (metadata from hello2.objtmp) and it was
being read in "text" mode. See man page for fopen().

Dave D