From: "Ken Yee" <kenkyee@excite.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: possible bug in configtool or whatever is generating "target.ld" file
Date: Thu, 27 Sep 2012 21:34:00 -0000 [thread overview]
Message-ID: <20120927173409.1868@web008.roc2.bluetie.com> (raw)
John Dallaway wrote:
> The fact that "SECTION_sram_code" appears in your target.ld output
> suggests that this macro is used in the target-specific .ldi file but is
> not defined in the architecture-specific .ld file and is therefore not
> being replaced by the C preprocessor.
That was it...thanks much :-)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2012-09-27 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 21:34 Ken Yee [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-27 3:46 [ECOS] " Ken Yee
2012-09-27 7:28 ` [ECOS] " John Dallaway
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=20120927173409.1868@web008.roc2.bluetie.com \
--to=kenkyee@excite.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).