This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: FW: Re: Why is my executabel in DOS file format?


"Meg Abyte" <fitter20@hotmail.com> writes:

> Are you sure /n =  is turing into a line feed ?  I don't think it is,
> thus I wouldn't need to run DOS2UNIX. I just tried it with the HEX
> values and  /n etc. I found  /n on my linux box is a CR and LF.
> Thus explaining the problem with the tools is that there is really a
> /CR/CR/LF due to your /r.  I will get back to you on the success of
> the change you suggested, they are compiling...

BFD opens the output file in binary mode, not text mode.  It then
outputs \r \n, which is ASCII 13 ASCII 10.

> I will get the spec in a place where you all can access it then since
> this seems to be the problem that you guys don't have the spec. Or I
> will post it here since it isn't that large.

We can all post specs:
    http://home.socal.rr.com/awi/srecords.htm

> Ian, I am not sure why you keep replying saying it is not a text file
> when I have QUOTED right out of the SPEC it is a text file - ASCII
> READABLE!
> 
> I can take a TEXT editor and TYPE IN the SREC using VI, and this works
> completely fine.

But you also quoted, apparently from the spec, /cr/lf/null.  That is
not the same as a text file, unless it means something other than what
I expect.  I'm not aware of any platform on which a text file can
contain ASCII 0.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]