From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vinson Lee <vlee@twopensource.com>
Cc: linux-next@vger.kernel.org, Daniel Mack <daniel@zonque.org>,
David Herrmann <dh.herrmann@googlemail.com>,
Djalal Harouni <tixxdz@opendz.org>
Subject: Re: next-20151002 build error "samples/kdbus/kdbus-workers.c:778: error: ‘CLOCK_MONOTONIC_COARSE’"
Date: Sat, 3 Oct 2015 13:21:01 +0200 [thread overview]
Message-ID: <20151003112101.GD22260@kroah.com> (raw)
In-Reply-To: <CAHTgTXXam2MA440R4hf+jZVaUYqtWERogPHHcosRv+kC2MUTEQ@mail.gmail.com>
On Fri, Oct 02, 2015 at 07:10:38PM -0700, Vinson Lee wrote:
> Hi.
>
> I am hitting this build error in kdbus-workers.c with Ubuntu 10.04.4.
> Ubuntu 10.04.4 has glibc 2.11.
Ugh, that's an old glibc :(
> HOSTCC samples/kdbus/kdbus-workers
> samples/kdbus/kdbus-workers.c: In function ‘child_run’:
> samples/kdbus/kdbus-workers.c:778: error: ‘CLOCK_MONOTONIC_COARSE’
> undeclared (first use in this function)
> samples/kdbus/kdbus-workers.c:778: error: (Each undeclared identifier
> is reported only once
> samples/kdbus/kdbus-workers.c:778: error: for each function it appears in.)
> samples/kdbus/kdbus-workers.c: In function ‘bus_open_connection’:
> samples/kdbus/kdbus-workers.c:1043: error: ‘O_CLOEXEC’ undeclared
> (first use in this function)
> samples/kdbus/kdbus-workers.c: In function ‘bus_make’:
> samples/kdbus/kdbus-workers.c:1280: error: ‘O_CLOEXEC’ undeclared
> (first use in this function)
> make[2]: *** [samples/kdbus/kdbus-workers] Error 1
As I don't have access to such ancient machines, could you work on a
patch for this, adding the needed defines if they aren't present by the
libc?
thanks,
greg k-h
prev parent reply other threads:[~2015-10-03 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 2:10 next-20151002 build error "samples/kdbus/kdbus-workers.c:778: error: ‘CLOCK_MONOTONIC_COARSE’" Vinson Lee
2015-10-03 11:21 ` Greg Kroah-Hartman [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=20151003112101.GD22260@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@zonque.org \
--cc=dh.herrmann@googlemail.com \
--cc=linux-next@vger.kernel.org \
--cc=tixxdz@opendz.org \
--cc=vlee@twopensource.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).