From: Al Viro Date: Tue, 06 Jan 2009 15:52:10 +0000 Subject: Re: ftrace breaks sparc64 build Message-Id: <20090106155210.GT28946@ZenIV.linux.org.uk> List-Id: References: <20090105181922.GA25622@uranus.ravnborg.org> <20090105194844.GR28946@ZenIV.linux.org.uk> <20090105195523.GB6204@uranus.ravnborg.org> <49631BF0.76E4.0078.0@novell.com> <20090106113543.GS28946@ZenIV.linux.org.uk> <20090106133442.GA14780@uranus.ravnborg.org> In-Reply-To: <20090106133442.GA14780@uranus.ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Sam Ravnborg Cc: Jan Beulich , "David S. Miller" , Ingo Molnar , rostedt@goodmis.org, Steven Rostedt , LKML , sparclinux On Tue, Jan 06, 2009 at 02:34:42PM +0100, Sam Ravnborg wrote: > On Tue, Jan 06, 2009 at 11:35:43AM +0000, Al Viro wrote: > > On Tue, Jan 06, 2009 at 07:53:04AM +0000, Jan Beulich wrote: > > > > > The __crc_... reference is definitely bogus - none should survive with the > > > new .c->.o rule. Could you find out what object file they originate from? > > > > So can you, by use of arcane tool known as "grep"... It's in kernel/softirq.c > > and that's genksyms parser being fucked in head. Look for TYPEOF_KEYW > > in parse.y and you'll see. Especially amusing part is a kludge from > > commit a89a0a2354ae666612968e254d650bfd04f11eb6... > > Any feedback on what to do to make it better? > Never used typeof myself so I do not know the exact syntax. Same as that of sizeof. I.e. typeof() or typeof .