From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] __attribute aligned and objcopy
Date: Thu, 25 Sep 2003 10:37:00 -0000 [thread overview]
Message-ID: <004001c38351$080aa1d0$73dea8c0@lair> (raw)
This is driving me nuts, and I can't seem to find a solution
to this on the net.
I have a romfs image that I try to convert to a .o file using:
# how do I add a __attribute((aligned(4))__ to objcopy?
arm-elf-objcopy -B arm -I binary -O elf32-littlearm --rename-section
.data=.rodata1 $*.rawdata $(OUTPUT)/$*_raw.o
This is used to mount a ROMFS:
extern "C"
{
extern const cyg_uint8 _binary___rom_rawdata_start[];
}
// this is not aligned to 4 bytes, and hence it does not work
sprintf( address, "%p", _binary___rom_rawdata_start);
err = mount( address, "rom", "romfs" );
Øyvind
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-09-25 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 10:37 Øyvind Harboe [this message]
2003-09-25 10:59 ` Gary Thomas
2003-09-25 13:51 ` Øyvind Harboe
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='004001c38351$080aa1d0$73dea8c0@lair' \
--to=oyvind.harboe@zylin.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).