From: Daniel Ann <ktdann@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Error compiling/linking
Date: Thu, 31 Mar 2005 14:06:15 +0900 [thread overview]
Message-ID: <9b7ca657050330210643d3ae15@mail.gmail.com> (raw)
In-Reply-To: <20050331012121.GA657@acmay.homeip.net>
Hi there <debian user>,
I've tried touching the file first, but with no luck. I didnt think
this would be the problem since it successfully creates the u-boot.map
file.
However, I'm not certain if it created the whole map file or not, but
if anyone is interested, last few lines of the map file reads,
////////////////////////////////////////
.rela.got
*(.rela.got)
.rel.ctors
*(.rel.ctors)
.rela.ctors
//////////////////////////////////////
As for now, I've filed bug report for binutil. We'll see if they have
better luck with it.
Cheers,
On Wed, 30 Mar 2005 17:21:21 -0800, Debian User <acmay@acmay.homeip.net> wrote:
> On Tue, Mar 29, 2005 at 08:31:06PM +0900, Daniel Ann wrote:
> > After trying the compilation from the command line, I've found out the
> > powerpc-linux-objdump was okay. But had segmentation fault during
> > powerpc-linux-ld.
> > So, doing rather simple trial and error method, I've got it compiled
> > after removing line which reads "-Map u-boot.map".
>
> Try a touch u-boot.map before the ld command. I have seen some ld's
> crash when the file isn't there. Never spent much time look at it
> or reporting it, but it isn't a problem on newer versions so I thought
> it was known/resolved.
>
--
Daniel
prev parent reply other threads:[~2005-03-31 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 1:58 [U-Boot-Users] Error compiling/linking Speed
2005-03-29 7:59 ` Wolfgang Denk
2005-03-29 11:31 ` Daniel Ann
2005-03-29 13:36 ` Wolfgang Denk
2005-03-31 1:21 ` Debian User
2005-03-31 5:06 ` Daniel Ann [this message]
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=9b7ca657050330210643d3ae15@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.