dhcpcd-discuss

On Sun, 1 Oct 2017 22:26:31 +0100
Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On 01/10/2017 20:48, M. Buecher wrote:
> > It builds except for one error:
> > ../../src/eloop.o: In function `eloop_event_add_rw':
> > ./src/eloop.c:353: undefined reference to `reallocarray'
> > collect2: error: ld returned 1 exit status
> > Makefile:39: recipe for target 'eloop-bench' failed
> > 
> > Don't know if this a source or Raspbian/Debian issue.
> > Anybody got a clue?  
> 
> I can replicate it on my Sparky Linux image.
> But it's tempermental, I can't always replicate it.

Might it be related to a race condition in parallel builds (-j #)? Sounds like occasionally a file (.h?) doesn't get built in time; I've seen this many times in my projects with '-j 8'. Said elsely, does it *not* happen with '-j 1'?

> 
> I *think* it's a bug with GNU make - I cannot replicate it on any BSD 
> platform but then reallocarray is also present so that particular issue 
> would never be hit either.
> 
> When it happens, I was able to build simply by touching src/eloop.c.
> This changes the datetime, which make does use, implying it's a make 
> issue, or maybe an issue with my Makefile, but I don't understand what 
> or how.
> 
> The eloop_bench isn't really a test, it just measures performance of the 
> chosen polling mechanism. I wrote it to highlight an issue with the 
> kqueue implementation on NetBSD compared to other BSDs. Linux of course 
> uses epoll.
> 
> Roy
>