linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jim Davis <jim.epost@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-next <linux-next@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Andi Kleen <ak@linux.intel.com>, Michal Marek <mmarek@suse.cz>
Subject: Re: linux-next: Tree for May 7 (argh)
Date: Thu, 8 May 2014 08:02:51 +1000	[thread overview]
Message-ID: <20140508080251.64eed8b579e307c25c46e27f@canb.auug.org.au> (raw)
In-Reply-To: <CA+r1ZhiUj3G44MWoacLg6fWD-eDFZ=3L8QbwuBvOB2JWAURDqQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

Hi Jim,

On Wed, 7 May 2014 14:45:59 -0700 Jim Davis <jim.epost@gmail.com> wrote:
>
> On 5/7/14, Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > I was away for one week.  Did I miss some new instructions about
> > building linux-next?
> >
> > I get a thousands of messages like these:
> >
> > WARNING: "system_wq" [drivers/misc/bh1770glc.ko] has no CRC!
> > WARNING: "__wake_up" [drivers/misc/bh1770glc.ko] has no CRC!
> > WARNING: "sysfs_notify" [drivers/misc/bh1770glc.ko] has no CRC!
> > WARNING: "kfree" [drivers/misc/bh1770glc.ko] has no CRC!
> 
> I don't recognized those, but
> 
> >
> >
> > Also there hundreds of messages like these:
> >
> > ps2mult.c:(.exit.text+0x8f): multiple definition of `cleanup_module'
> > ps2mult.c:(.init.text+0xbc8): multiple definition of `init_module'
> > ipack.c:(.exit.text+0x0): multiple definition of `cleanup_module'
> > ipack.c:(.init.text+0x0): multiple definition of `init_module'
> > mcb-core.c:(.text+0x40d): multiple definition of `cleanup_module'
> > mcb-core.c:(.text+0x3fb): multiple definition of `init_module'
> 
> I had to hardwire CONFIG_LTO_MENU=n to avoid lots of linker complaints
> about standard library things (strcmp, etc.).  This is on a Ubuntu
> 14.04 system.

The CONFIG_LTO... stuff has been in linux-next since (at least)
next-20140408, so maybe something else has impacted on it?  Or have you
had to do the above since then?  If so, what config, what arch?

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-07 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  7:33 linux-next: Tree for May 7 Stephen Rothwell
2014-05-07 20:52 ` linux-next: Tree for May 7 (argh) Randy Dunlap
2014-05-07 21:45   ` Jim Davis
2014-05-07 22:02     ` Stephen Rothwell [this message]
2014-05-07 22:17       ` Jim Davis
2014-05-08  1:10         ` Andi Kleen
2014-05-08 16:54           ` Randy Dunlap
2014-05-08 17:05           ` Jim Davis
2014-05-08 17:08             ` Andi Kleen
2014-05-08 17:40               ` Jim Davis
2014-05-07 21:56   ` Stephen Rothwell
2014-05-07 22:31     ` Randy Dunlap

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=20140508080251.64eed8b579e307c25c46e27f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ak@linux.intel.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rdunlap@infradead.org \
    --cc=rusty@rustcorp.com.au \
    /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).