public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
* kbuild, modpost: fix "non-allocatable section" warnings
@ 2009-05-04 11:57 Sam Ravnborg
  2009-05-04 11:59 ` [PATCH 1/3] kbuild, modpost: fix unexpected non-allocatable section when cross compiling Sam Ravnborg
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Sam Ravnborg @ 2009-05-04 11:57 UTC (permalink / raw)
  To: LKML, linux-kbuild
  Cc: Sean MacLennan, Anders Kaseorg, Jean Delvare, Manuel Lauss,
	Stephen Rothwell, linuxppc-dev, Wolfgang Denk

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-05-04 11:59 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-04 11:57 kbuild, modpost: fix "non-allocatable section" warnings Sam Ravnborg
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox