From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Stephen Hemminger <shemminger@vyatta•com>
Cc: David Miller <davem@davemloft•net>,
netdev@vger•kernel.org, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org, jchapman@katalix•com
Subject: Section msimatch warnings (Was: Re: linux-next: build failure after merge of the final tree (net-current tree related))
Date: Tue, 26 Oct 2010 10:04:27 +1100 [thread overview]
Message-ID: <20101026100427.f7c30b3d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20101025103636.442e108a@nehalam>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Hi Stephen,
On Mon, 25 Oct 2010 10:36:36 -0700 Stephen Hemminger <shemminger@vyatta•com> wrote:
>
> The section mismatch warning on x86 is not shown by default
> because there are still so many problems.
This is actually different - it is generated by the compiler. I am not
sure why we only get them on PowerPC. Rusty suggested that we could
dynamically create a file that just referenced all the EXPORTed symbols
(we know what they are) and try to link that. Then we would find all the
static ones. PowerPC would still find them earlier, of course, but since
a lot of poeple only compile for x86(_64), they may not get as far as the
PowerPC builds.
The other section mismatch warnings (generated by an external program)
are certainly suppressed by default on all architectures. I enable them
for some of my builds, and it is not too bad at the moment (apart from a
couple of particular subsystems - and Sparc :-)). I suspect that if we
reenabled them by default, they would be fixed fairly quickly.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-10-25 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 3:19 linux-next: build failure after merge of the final tree (net-current tree related) Stephen Rothwell
2010-10-25 5:26 ` David Miller
2010-10-25 17:36 ` Stephen Hemminger
2010-10-25 23:04 ` Stephen Rothwell [this message]
2010-10-25 23:27 ` Section msimatch warnings David Miller
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=20101026100427.f7c30b3d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=jchapman@katalix$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
/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