From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Debug build fails
Date: Mon, 29 Sep 2008 17:02:36 +0000 [thread overview]
Message-ID: <1222707756.20695.5.camel@lgn.site> (raw)
In-Reply-To: <48E1074D.5010703@tuffmail.co.uk>
On Mon, 2008-09-29 at 17:50 +0100, Alan Jenkins wrote:
> udevadm-info.c: In function ‘print_all_attributes’:
> udevadm-info.c:65: error: ‘udev’ undeclared (first use in this function)
> udevadm-info.c:65: error: (Each undeclared identifier is reported only once
> udevadm-info.c:65: error: for each function it appears in.)
> udevadm-info.c:72: error: ‘info’ undeclared (first use in this function)
>
>
> The dbg() macro sucks. The disabled version should be an inline
> function, so it catches these errors on normal builds.
Sounds good.
> Obviously the callers need to be fixed before this can be applied.
Done.
> Allow compiler to check dbg() arguments on non-debug builds
Applied.
Thanks,
Kay
prev parent reply other threads:[~2008-09-29 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 16:50 Debug build fails Alan Jenkins
2008-09-29 17:02 ` Kay Sievers [this message]
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=1222707756.20695.5.camel@lgn.site \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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).