This is OK, you may ignore this message. Configure scripts, generated by autoconf are trying to delete "core" files during their work, as they expect that some operations can generate coredump files on crash, so it prints this error when it faces "core" directory. More details here: [1].
The short answer is - you can safely ignore this message. [1] - https://lists.gnu.org/archive/html/autoconf/2012-12/msg00001.html Best Regards, Igor On Tue, Aug 7, 2018 at 4:24 PM Floris Van Nee <florisvan...@optiver.com> wrote: > Hi, > > > > I’m trying to build Apache Ignite C++ from source on Ubuntu. First, I > downloaded the Ignite 2.6 source code and built the Java part. This was > successful. Then, I went to the modules/platforms/cpp directory and ran: > > libtoolize && aclocal && autoheader && automake --add-missing && > autoreconf > > > > This completed successfully as well. After that, ./configure exited with > the following error: > > > > config.status: executing depfiles commands > > config.status: executing libtool commands > > rm: cannot remove 'core': Is a directory > > > > (This cannot remove ‘core’ message is displayed more often in the output). > It seems it is trying to remove the directory ‘core’, but I don’t know why. > Has anyone seen this problem before? > > > > -Floris >
