public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: bartv@redhat.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Enable thumb interworking?
Date: Fri, 09 Feb 2001 12:55:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010209155107.00b33e50@larwe.com> (raw)
In-Reply-To: <200102091840.f19IeWD26571@sheesh.cambridge.redhat.com>

Hi again Bart,

>    Lewin> Secondly, why is the ecos/install/lib/target.ld file always
>     Lewin> generated incorrectly by ecosconfig? The spacing is all
>     Lewin> screwed; every word has a carriage return after it. I have
>
>generated by the C preprocessor, or some of the files being #include'd
>contain spurious carriage returns e.g. because they were just copied
>directly from a Windows box. I have never seen the actual behaviour
>you describe, so you'll have to investigate further. Problems with the

I could understand that... I have redownloaded _all_ the components using 
Linux (so every text file I have, particularly thinking here of CVS stuff, 
should now be UNIX-EOL-convention), I will try it out later this afternoon.

It is odd that it's only this one file affected. Is there no other 
intermediate file in eCos that's generated with the same process?

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."

  reply	other threads:[~2001-02-09 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 12:02 Lewin A.R.W. Edwards
2001-02-09 10:40 ` Bart Veer
2001-02-09 12:55   ` Lewin A.R.W. Edwards [this message]
2001-02-12  7:01     ` Bart Veer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4.3.2.7.2.20010209155107.00b33e50@larwe.com \
    --to=larwe@larwe.com \
    --cc=bartv@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).