From: Lars Poeschel <larsi@wh2.tu-dresden.de>
To: ecos-devel@ecos.sourceware.org
Subject: Strange buildsystem behaviour
Date: Wed, 18 Jun 2008 09:36:00 -0000 [thread overview]
Message-ID: <92187523-464B-4EFE-A03F-AA54E4AD3E6A@wh2.tu-dresden.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
Hello!
I am currently working on flash support for fr30, skmb91302 platform.
I added some code to platform.S file. I want to build a redboot image
now and the following happens:
platform.S gets assembled to hal_fr30_skmb91302_platform.o and then
added to libtarget.a correctly.
I can verify that the contents is there and correct with objdump.
Then redboot gets build, but the image (redboot.elf) does not contain
my new code! The Linker seems to throw it away.
But when I copy the code from platform.S and paste it as it is without
modification into variant.S(the .sections are the same), at first the
same happens. The code gets assembled to hal_fr30_mb91301_variant.o
and added to libtarget.a. But then redboot builds and the resulting
image contains the code!
The linker script I use has no special rule for platform or variant
files.
Does anybody have a hint for me ? How can I get the code linked when
it is in platform.S ?
Thanks,
Lars
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2008-06-18 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 9:36 Lars Poeschel [this message]
2008-06-18 9:53 ` Andrew Lunn
2008-06-18 10:07 ` Lars Poeschel
2008-06-18 10:23 ` Andrew Lunn
2008-06-18 10:58 ` Lars Poeschel
2008-06-18 16:26 ` Partition support for FAT file system Frank Pagliughi
2008-06-18 16:44 ` Nick Garnett
2008-06-18 17:01 ` Frank Pagliughi
2008-06-18 19:26 ` Nick Garnett
2008-06-20 13:56 ` Frank Pagliughi
2008-06-18 19:28 ` Frank Pagliughi
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=92187523-464B-4EFE-A03F-AA54E4AD3E6A@wh2.tu-dresden.de \
--to=larsi@wh2.tu-dresden.de \
--cc=ecos-devel@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).