I have not been able to reproduce this myself but I have seen a build log where
the binary tries to link to libeo and fails due to the missing file.
A similar problem was "fixed" in
0e4b847deb79c957dbc042ea0c6a98282aead6e0, but
this really makes me wonder where the linking against eo comes from for cserve2
which is not using eo as far as I can see.
@EVAS_CFLAGS@
bin_evas_evas_cserve2_slave_LDADD = @EVAS_CSERVE2_SLAVE_LIBS@ @USE_EINA_LIBS@
-bin_evas_evas_cserve2_slave_DEPENDENCIES = @USE_EINA_INTERNAL_LIBS@
+bin_evas_evas_cserve2_slave_DEPENDENCIES = @USE_EINA_INTERNAL_LIBS@ @USE_EO_INTERNAL_LIBS@
bin_evas_evas_cserve2_slave_LDFLAGS = -export-dynamic
bin_evas_dummy_slave_SOURCES = \