LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "kus Kusche Klaus" <kus@keba.com> To: <linux-kernel@vger.kernel.org>, "Ingo Molnar" <mingo@elte.hu>, "Thomas Gleixner" <tglx@linutronix.de> Subject: [RT] Compile error with certain IRQ debug config option combinations Date: Thu, 14 Feb 2008 16:48:05 +0100 [thread overview] Message-ID: <AAD6DA242BC63C488511C611BD51F367032B8BA5@MAILIT.keba.co.at> (raw) I'm using 2.6.24.2 with -rt1 applied (applies cleanly with some offsets) on x86. I've *not* configured PROVE_LOCKING (too expensive). However, I selected all the latency tracings, timings and histograms, among them CRITICAL_IRQSOFF_TIMING. This implicitly configures TRACE_IRQFLAGS. However, TRACE_IRQFLAGS depends on PROVE_LOCKING, which is off (and not implicitly selected). With TRACE_IRQFLAGS on and PROVE_LOCKING off, compilation of kernel/lockdep.c fails miserably: CC kernel/lockdep.o kernel/lockdep.c: In function 'check_usage_forwards': kernel/lockdep.c:1740: error: 'find_usage_bit' undeclared (first use in this function) kernel/lockdep.c:1740: error: (Each undeclared identifier is reported only once kernel/lockdep.c:1740: error: for each function it appears in.) kernel/lockdep.c:1742: error: implicit declaration of function 'find_usage_forwards' kernel/lockdep.c:1746: error: 'forwards_match' undeclared (first use in this function) kernel/lockdep.c: In function 'check_usage_backwards': kernel/lockdep.c:1759: error: 'find_usage_bit' undeclared (first use in this function) kernel/lockdep.c:1761: error: implicit declaration of function 'find_usage_backwards' kernel/lockdep.c:1765: error: 'backwards_match' undeclared (first use in this function) make[1]: *** [kernel/lockdep.o] Error 1 Looking at the source quickly, it seems that the #ifdefs do not cover that combination correctly, but I can't figure out how to fix that (the ifdef nesting in that file seems to have grown over time...). By the way: With all the tracing on, make also tries to compile scripts/trace-it.c (with HOSTCC), which also fails if the kernel is cross-compiled in a non-linux development environment (Interix in my case - don't ask me, I didn't vote for it...). Many thanks in advance for any help! Greetings -- Klaus Kusche, DI. Dr. Software Development - Control KEBA AG Gewerbepark Urfahr, A-4041 Linz, Austria www.keba.com Firmenbuchgericht Linz FN 184376 t mailto:kus@keba.com Phone: +43 732 7090-23120 Fax: +43 732 7090-63401
reply other threads:[~2008-02-14 16:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AAD6DA242BC63C488511C611BD51F367032B8BA5@MAILIT.keba.co.at \ --to=kus@keba.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=tglx@linutronix.de \ /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: linkBe 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).