public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: larwe@larwe.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Enable thumb interworking?
Date: Fri, 09 Feb 2001 10:40:00 -0000	[thread overview]
Message-ID: <200102091840.f19IeWD26571@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010208150039.00b51890@larwe.com>

>>>>> "Lewin" == Lewin A R W Edwards <larwe@larwe.com> writes:

    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
    Lewin> to copy the linker script from my Windows machine in order
    Lewin> to link at all.

target.ld is not build by ecosconfig, it is built by a custom build
step defined in the CDL for the architectural HAL package. For an ARM
processor that means the following:

        <PREFIX>/lib/target.ld: <PACKAGE>/src/arm.ld
        $(CC) -E -P -Wp,-MD,target.tmp -DEXTRAS=1 -xc $(INCLUDE_PATH) $(CFLAGS) -o $@ $<
        @echo $@ ": \\" > $(notdir $@).deps
        @tail +2 target.tmp >> $(notdir $@).deps
        @echo >> $(notdir $@).deps
        @rm target.tmp

The first command is the important one. Essentially it passes the
arm.ld file from the src subdirectory of the ARM architectural HAL
package through the C preprocessor. It ends up #include'ing a
file provided by the platform HAL which supplies information such as
what memory is actually available.

If you are seeing spurious carriage returns then either these are
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
C preprocessor should be reported to the appropriate gcc mailing list.

Bart

  reply	other threads:[~2001-02-09 10:40 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 [this message]
2001-02-09 12:55   ` Lewin A.R.W. Edwards
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=200102091840.f19IeWD26571@sheesh.cambridge.redhat.com \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=larwe@larwe.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).