From: Sam Ravnborg <sam@ravnborg.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Wolfgang Denk <wd@denx.de>,
Manuel Lauss <mano@roarinelk.homelinux.net>,
Anders Kaseorg <andersk@mit.edu>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Sean MacLennan <smaclennan@pikatech.com>,
Jean Delvare <khali@linux-fr.org>
Subject: kbuild, modpost: fix "non-allocatable section" warnings
Date: Mon, 4 May 2009 13:57:04 +0200 [thread overview]
Message-ID: <20090504115704.GA7134@uranus.ravnborg.org> (raw)
It turned out there were at least three sources of
the "non-allocatable section" warning.
1) SUSE specific .comment section
2) endianness issues in elf header
3) additional debug sections
I have updated kbuild-fixes.git with
patches for all of the above.
But as we have seen three independent sources of this
warning within short time I expect there may be
yet-to-be-discovered issues.
The patches accumulated so far all looks trivially correct
and Jean and Sean has been quick to test them.
So unless something unexpected shows up I plan to push them
within a day or two.
I would like to see them in -next for a day or two first
in the hope that if other architectures has troubles
they will report this before it hits upstream.
Patches will follow for reference / testing.
Sam
next reply other threads:[~2009-05-04 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 11:57 Sam Ravnborg [this message]
2009-05-04 11:59 ` [PATCH 1/3] kbuild, modpost: fix unexpected non-allocatable section when cross compiling Sam Ravnborg
2009-05-04 12:00 ` [PATCH 2/3] kbuild, modpost: fix "unexpected non-allocatable" warning with SUSE gcc Sam Ravnborg
2009-05-04 12:01 ` [PATCH 3/3] kbuild, modpost: fix unexpected non-allocatable warning with mips 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=20090504115704.GA7134@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=andersk@mit.edu \
--cc=khali@linux-fr.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mano@roarinelk.homelinux.net \
--cc=sfr@canb.auug.org.au \
--cc=smaclennan@pikatech.com \
--cc=wd@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 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).