linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andi Kleen <ak@linux.intel.com>, Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next <linux-next@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Michal Marek <mmarek@suse.cz>
Subject: Re: linux-next: Tree for May 7 (argh)
Date: Thu, 08 May 2014 09:54:44 -0700	[thread overview]
Message-ID: <536BB6D4.8020309@infradead.org> (raw)
In-Reply-To: <20140508011030.GT19657@tassilo.jf.intel.com>

On 05/07/2014 06:10 PM, Andi Kleen wrote:
>>>>> 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'
>>>>
> 
> It sounds like it misdetects your binutils. LTO should
> disable itself when your binutils cannot handle it. Can you send me
> the full build log and output of ld --version and gcc --version
> please?

Hi Andi,

I see this message:
scripts/Makefile.lto:82: "WARNING: GCC 0407 too old for LTO/WHOPR. CONFIG_LTO disabled"

so that seems to be working OK.

I think that the init_module/cleanup_module problems are due to some errors
in my automated scripts.  Sorry about that.  Please ignore my original report.


-- 
~Randy

  reply	other threads:[~2014-05-08 16:54 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
2014-05-07 22:17       ` Jim Davis
2014-05-08  1:10         ` Andi Kleen
2014-05-08 16:54           ` Randy Dunlap [this message]
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=536BB6D4.8020309@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.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).