From: Sam Ravnborg <sam@ravnborg•org>
To: Wolfgang Denk <wd@denx•de>
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Sean MacLennan <smaclennan@pikatech•com>
Subject: Re: unexpected non-allocatable section
Date: Sun, 3 May 2009 22:51:03 +0200 [thread overview]
Message-ID: <20090503205103.GA1506@uranus.ravnborg.org> (raw)
In-Reply-To: <20090503201940.82D3083420E8@gemini.denx.de>
> I ran the tests on a LE machine:
>
> Linux gemini.denx.de 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686 i686 i386 GNU/Linux
>
> > I will push the patch in a few minutes.
> >
> > For reference it is below:
> >
> > Sam
> >
> > From: Anders Kaseorg <andersk@MIT•EDU>
> > Subject: [PATCH] kbuild, modpost: fix unexpected non-allocatable section when cross compiling
> >
> > The missing TO_NATIVE(sechdrs[i].sh_flags) was causing many
> > unexpected non-allocatable section warnings when cross-compiling
> > for an architecture with a different endianness.
>
> I'm confused. Why didn't I see this, then?
Maybe they just scrolled past the screen first time?
You need to do "rm vmlinux.o" to reproduce it.
The warnings are shown when we do section mismatch analysis on vmlinux.o
which is part of the final steps in creating vmlinux.
But you will force the check again if you only delete vmlinux.
You need to delete vmlinux.o to see them.
I hope this is the explanation - otherwise I have no good idea.
Sam
next prev parent reply other threads:[~2009-05-03 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 2:41 unexpected non-allocatable section Sean MacLennan
2009-05-03 7:04 ` Sean MacLennan
2009-05-03 10:45 ` Stephen Rothwell
2009-05-03 16:39 ` Sean MacLennan
2009-05-03 19:33 ` Wolfgang Denk
2009-05-03 20:07 ` Sam Ravnborg
2009-05-03 20:19 ` Wolfgang Denk
2009-05-03 20:51 ` Sam Ravnborg [this message]
2009-05-03 20:32 ` Sean MacLennan
2009-05-03 20:51 ` Sam Ravnborg
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=20090503205103.GA1506@uranus.ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=smaclennan@pikatech$(echo .)com \
--cc=wd@denx$(echo .)de \
/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