On Mon, 2012-01-09 at 07:42 -0800, Greg KH wrote: > > > 8a25a2fd126c621f44f3aeaef80d51f00fc11639 is the first bad commit > > commit 8a25a2fd126c621f44f3aeaef80d51f00fc11639 > > Author: Kay Sievers <kay.sievers@xxxxxxxx> > > Date: Wed Dec 21 14:29:42 2011 -0800 > > > > cpu: convert 'cpu' and 'machinecheck' sysdev_class to a regular subsystem > > How is this triggering this build problem? I didn't see this happen > before, and it wasn't showing up in linux-next in the past, right? > > This patch has nothing to to with tracing, perhaps it is an #include > file problem? Or is the build error a different one (remember the > -Werror problem in linux-next that I fixed up for PPC?) I'll take a look at this today. The problem is that something probably included one of the "include/trace/event/*.h" files in a header. That's always a pain, as those files should not be in headers and only called by C files that directly use tracepoints. Those headers have the macro magic to create those undefined symbols that Stephen is seeing and when you have one trace/event/*.h included in another, it can sometimes cause strange side effects like this. Thus, simply adding an "include" somewhere can trigger this. I'll checkout latest mainline and see. Stephen, what config does this trigger with? Thanks, -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
