> I recall the other reason for that change now, too. eval-modules.c isn't
> currently removed on "make spotless", leading to odd recompilation
> behaviour and potentially broken "make dist" results since file
> timestamps will not be correctly "ordered" if you build, clean, and
> rebuild (import l
I recall the other reason for that change now, too. eval-modules.c isn't
currently removed on "make spotless", leading to odd recompilation
behaviour and potentially broken "make dist" results since file
timestamps will not be correctly "ordered" if you build, clean, and
rebuild (import libraries n
> Whoops, no, they are not correct. I wanted to put eval-modules-static.o
> in the static object list (i.e. LIBCHICKEN_STATIC_OBJECTS), not both.
>
> Please see the attached patch for a correction. This one does what I was
> trying to do the first time.
Thanks, Evan. Signed off and pushed.
feli
Hi Felix,
On 2018-03-05 14:49, felix.winkelm...@bevuta.com wrote:
> Are you sure this is correct? These commits
Whoops, no, they are not correct. I wanted to put eval-modules-static.o
in the static object list (i.e. LIBCHICKEN_STATIC_OBJECTS), not both.
Please see the attached patch for a correc
