From: John Dallaway <john@dallaway.org.uk>
To: Ken Yee <kenkyee@excite.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: possible bug in configtool or whatever is generating "target.ld" file
Date: Thu, 27 Sep 2012 07:28:00 -0000 [thread overview]
Message-ID: <5063FFFC.2020405@dallaway.org.uk> (raw)
In-Reply-To: <20120926234606.868@web002.roc2.bluetie.com>
Hi Ken
On 27/09/12 04:46, Ken Yee wrote:
> When you link your app, the symptom is you see this when you link your application:
>
> /home/ecos/gnutools/arm-eabi/bin/../lib/gcc/arm-eabi/4.6.2/../../../../arm-eabi/bin/ld:target.ld:17: syntax error
> collect2: ld returned 1 exit status
>
> It's a bit of a cryptic error because target.ld is not in the path indicated.
> It's actually in your your ecos_install/lib directory.
> If you open the target.ld file, you'll see this:
>
> ==============
> ...
> SECTIONS
> {
> .debug_aranges 0 : { *(.debug_aranges) } .debug_pubnames 0 : { *(.debug_pubnames) } .debug_info 0 : { *(.debug_info) } .debug_abbrev 0 : { *(.debug_abbrev) } .debug_line 0 : { *(.debug_line) } .debug_frame 0 : { *(.debug_frame) } .debug_str 0 : { *(.debug_str) } .debug_loc 0 : { *(.debug_loc) } .debug_macinfo 0 : { *(.debug_macinfo) } .note.arm.ident 0 : { KEEP (*(.note.arm.ident)) } /DISCARD/ 0 : { *(.fini_array*) }
> .fixed_vectors 0x20 : { . = .; KEEP (*(.fixed_vectors)) } > sram
> SECTION_sram_code (sram, ALIGN (0x4), )
> .rom_vectors 0x02008000 : { __rom_vectors_vma = ABSOLUTE(.); . = .; KEEP (*(.vectors)) } > ram __rom_vectors_lma = LOADADDR(.rom_vectors);
> ...
> ================
>
> The offending line 17 is the one that starts with SECTION_sram_code; delete this
> line to fix the link error.
> That looks like the syntax for the .ldi file instead of the target.ld file.
The eCos build system runs the C preprocessor over a target-specific
.ldi file to generate the final linker script file (target.ld). The
macros such as SECTION_data and SECTION_bss are defined in an
architecture-specific .ld file located in the relevant architecture HAL
package. For example, the Cortex-M architectural HAL package provides
the file src/cortexm.ld containing these definitions.
The various .ldi files provided by the platform HAL packages should use
only those macros defined in the relevant architecture-specific .ld
file. 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.
I hope this helps...
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
--
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 prev parent reply other threads:[~2012-09-27 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 3:46 [ECOS] " Ken Yee
2012-09-27 7:28 ` John Dallaway [this message]
2012-09-27 21:34 [ECOS] " Ken Yee
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=5063FFFC.2020405@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=kenkyee@excite.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).