From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-24
Date: Sun, 27 Jul 2014 07:52:19 +0300 [thread overview]
Message-ID: <20140727045219.GA2480@tarshish> (raw)
In-Reply-To: <CAMo8BfJ96eqY5hHU-Y8=MPAP48DbC6=tYZ90c0r7FgtoVGYjGQ@mail.gmail.com>
Hi Max,
On Sun, Jul 27, 2014 at 02:49:46AM +0400, Max Filippov wrote:
> On Fri, Jul 25, 2014 at 10:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Build statistics for 2014-07-24
> > xtensa | network-manager-0.9.10.0 | NOK | http://autobuild.buildroot.net/results/d33ed1c3bf1be7c8f8ea02590a770b0d29c7d9fa/
>
> It fails with
>
> NetworkManagerUtils.c:1020:23: error: 'CLOCK_BOOTTIME' undeclared
> (first use in this function)
> err = clock_gettime (CLOCK_BOOTTIME, tp);
>
> because there's no CLOCK_BOOTTIME in uClibc.
> Not sure what's the proper fix for that, adding support for
> CLOCK_BOOTTIME into uClibc?
> (looks fairly easy). Or just disabling network manager on uClibc?
A less intrusive solution might be adding
#ifndef CLOCK_BOOTTIME
#define CLOCK_BOOTTIME 7
#endif
in NetworkManagerUtils.c.
Adding CLOCK_BOOTTIME to uClibc sounds like a good idea anyway. I wonder
though why we see so few build failures like this one (only two at
http://autobuild.buildroot.net/?reason=network-manager-0.9.10.0 at the
moment).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-07-27 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-24 Thomas Petazzoni
2014-07-26 22:49 ` Max Filippov
2014-07-27 4:52 ` Baruch Siach [this message]
2014-07-27 19:43 ` Peter Korsgaard
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=20140727045219.GA2480@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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