Actually I have a build break in pu on my mac right now. Seems to
build fine in ubuntu, but:
progress.c:66:15: error: use of undeclared identifier 'CLOCK_MONOTONIC'
timer_create(CLOCK_MONOTONIC, &sev, &progress_timer);
^
./git-compat-util.h:233:54: note: expanded from macro 'timer_create'
#define timer_create(clockid, sevp, timerp) ((void) (clockid), (void) (s...
^
progress.c:71:2: warning: incompatible pointer to integer conversion assigning
to '__darwin_time_t' (aka 'long') from '__darwin_time_t *' (aka 'long *');
remove & [-Wint-conversion]
timer_settime(progress_timer, 0, &value, NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./git-compat-util.h:242:29: note: expanded from macro 'timer_settime'
_ivalue.it_interval.tv_sec = value.it_interval.tv_sec;
\
^ ~~~~~~~~~~~~~~~~~~~~~~~~
progress.c:71:2: error: invalid operands to binary expression
('long *' and 'long')
timer_settime(progress_timer, 0, &value, NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./git-compat-util.h:243:58: note: expanded from macro 'timer_settime'
_ivalue.it_interval.tv_usec = value.it_interval.tv_nsec /
1000L; \
~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~~
progress.c:71:2: error: use of undeclared identifier '_ivalue_it_value'
./git-compat-util.h:245:2: note: expanded from macro 'timer_settime'
_ivalue_it_value.tv_usec = value.it_value.tv_nsec / 1000L...
^
progress.c:71:2: error: invalid operands to binary expression
('long *' and 'long')
timer_settime(progress_timer, 0, &value, NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./git-compat-util.h:245:52: note: expanded from macro 'timer_settime'
_ivalue_it_value.tv_usec = value.it_value.tv_nsec / 1000L;
\
~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~~
progress.c:71:35: warning: expression result unused [-Wunused-value]
timer_settime(progress_timer, 0, &value, NULL);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
./git-compat-util.h:244:27: note: expanded from macro 'timer_settime'
_ivalue.it_value.tv_sec value.it_value.tv_sec...
^
progress.c:74:1: error: expected 'while' in do/while loop
static void clear_progress_signal(void)
^
progress.c:71:2: note: to match this 'do'
timer_settime(progress_timer, 0, &value, NULL);
^
./git-compat-util.h:240:52: note: expanded from macro 'timer_settime'
...flags, value, ovalue) do { \
^
progress.c:264:2: error: expected '}'
}
^
progress.c:50:1: note: to match this '{'
{
^
2 warnings and 6 errors generated.
make: *** [progress.o] Error 1
On Sun, Nov 9, 2014 at 12:04 PM, Torsten Bögershausen <tbo...@web.de> wrote:
> On 09.11.14 18:34, Michael Blume wrote:
>> Works for me, thanks =)
>>
>> I'm curious now, is there an automated build of git running on a mac
>> anywhere? There's a mac mini running jenkins in my office and it's
>> possible I could convince someone to let me set up a git build that'll
>> e-mail me if there's a test failure.
>
> The basic idea is to run
> make clean &&
> git fetch git.git &&
> git checkout git.git/pu &&
> make -k test
>
> (and pipe stdlog+stdout into a file)
>
> I have a script here doing that, if you want, I can send it to you
>
>
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
