Hi Jim, On Wed, 7 May 2014 14:45:59 -0700 Jim Davis wrote: > > On 5/7/14, Randy Dunlap 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