From: Felix Domke <tmbinc@elitedvb•net>
To: linuxppc-embedded@lists•linuxppc.org
Subject: file alignment of elf sections
Date: Tue, 11 Feb 2003 04:39:03 +0100 [thread overview]
Message-ID: <3E487057.8000100@elitedvb.net> (raw)
hi,
i'm currently porting u-boot to a ppc405-based board, but i'm failing
miserably at the first step - correct linking.
to make it short (and keep it a bit ontopic, sorry):
how can i tell ld to align the section in the FILE to 2^16 ? i have my
.text-section started at (loading address) 5MB, and like to have it in
the elf-file at 64k. i saw lds producing exactly this output, but in my
case the .text-section starts immediately after the elf header. (the
reason is that i have to convert the binary to a special format for the
primary bootloader, and the tool for converting is rather dumb, but i
don't want to invest time into fixing the tool since i didn't wrote it
and nobody else cares about it).
There must be a simple option, but i can't find it :/ (even after
googling around)
I have to admit that i did this before, but i can't remember HOW i did it.
felix
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-02-11 3:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E487057.8000100@elitedvb.net \
--to=tmbinc@elitedvb$(echo .)net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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