From: Segher Boessenkool <segher@kernel.crashing.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: section .dummy lma 0xc0294310 overlaps previous sections
Date: Fri, 25 Jul 2008 00:29:28 +0200 [thread overview]
Message-ID: <c7d136a69bb02682bf5f3dbbd658d975@kernel.crashing.org> (raw)
In-Reply-To: <20080724001857.42fc7e09@lappy.seanm.ca>
> Anybody else seeing these? With Linus' latest I get three of these
> warnings: .tmp_vmlinux1, .tmp_vmlinux2, and vmlinux.
Ah, that's useful information, I think I know what's going on
now. What was your binutils version?
Segher
next prev parent reply other threads:[~2008-07-24 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 4:18 section .dummy lma 0xc0294310 overlaps previous sections Sean MacLennan
2008-07-24 22:29 ` Segher Boessenkool [this message]
2008-07-24 23:17 ` Sean MacLennan
2008-07-24 23:43 ` Sean MacLennan
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=c7d136a69bb02682bf5f3dbbd658d975@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.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 NNTP newsgroup(s).