From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: 787066-forwarded@bugs.debian.org
Subject: Re: FTBFS with clang instead of gcc
Date: Mon, 27 Jul 2015 12:34:38 -0400 [thread overview]
Message-ID: <1837827.kIU5ZZHVo5@x2> (raw)
In-Reply-To: <20150726214950.GC27014@in.waw.pl>
On Sunday, July 26, 2015 09:49:50 PM Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Jul 26, 2015 at 03:58:44PM +0200, Laurent Bigonville wrote:
> > Apparently audit is FTBFS with clang due to the embedded version of
> > libev with the following error (see: [0]):
> >
> > ../../../../src/libev/ev.c:970:42: error: '_Noreturn' keyword must
> > precede function declarator
> >
> > The bug[0] provides a patch. I don't think this has been fixed
> > upstream yet. There was however a small thread [1] about this on
> > upstream ML.
> >
> Not sure what's the policy regarding patching embedded copy of libev.
> The policy is to kill the embedded copy as soon as possible.
> Seems like a good time to do that.
Not sure if you've ever had any dealings with upstream libev or not. But let's
just say its not easy. I apply a patch on top of libev to suit audit's needs.
https://fedorahosted.org/audit/changeset/782
Without this, coverity analysis is much harder. Audit is one of those
subsystems that you really need to be sure of what its doing and that even
libraries it uses are correct.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2015-07-27 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 13:58 FTBFS with clang instead of gcc Laurent Bigonville
2015-07-26 21:49 ` Zbigniew Jędrzejewski-Szmek
2015-07-27 16:34 ` Steve Grubb [this message]
2015-07-27 16:40 ` Zbigniew Jędrzejewski-Szmek
2015-07-27 16:50 ` Steve Grubb
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=1837827.kIU5ZZHVo5@x2 \
--to=sgrubb@redhat.com \
--cc=787066-forwarded@bugs.debian.org \
--cc=linux-audit@redhat.com \
/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).