Ignite 1.8 c++ Platform installation issue

[Shashank Gandham]

The ./configure command produces the following error:

configure: creating ./config.status
config.status: creating Makefile
config.status: creating core-test/include/Makefile
config.status: creating core-test/Makefile
config.status: creating common/os/linux/include/Makefile
config.status: creating common/include/Makefile
config.status: creating common/Makefile
config.status: creating binary/include/Makefile
config.status: creating binary/Makefile
config.status: creating odbc/include/Makefile
config.status: creating odbc/Makefile
config.status: creating odbc-test/include/Makefile
config.status: creating odbc-test/Makefile
config.status: creating core/include/Makefile
config.status: creating core/Makefile
config.status: creating core/ignite.pc
config.status: creating jni/include/Makefile
config.status: creating jni/Makefile
config.status: creating ignite/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
rm: cannot remove 'core': Is a directory

Does this need some fixing, or am I missing some steps?

[Igor Sapego]

Hi,

This is not an error. It comes from the Automake buildsystem considers
files named "core" to be a coredumps and tries to remove them. Ignite C++
has library named "core" with corresponding directory.

Shortly speaking, just ignore this message.

Best Regards,
Igor

On Sun, Feb 19, 2017 at 12:45 PM, Shashank Gandham <
[hidden email]> wrote:

> The ./configure command produces the following error:
>
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating core-test/include/Makefile
> config.status: creating core-test/Makefile
> config.status: creating common/os/linux/include/Makefile
> config.status: creating common/include/Makefile
> config.status: creating common/Makefile
> config.status: creating binary/include/Makefile
> config.status: creating binary/Makefile
> config.status: creating odbc/include/Makefile
> config.status: creating odbc/Makefile
> config.status: creating odbc-test/include/Makefile
> config.status: creating odbc-test/Makefile
> config.status: creating core/include/Makefile
> config.status: creating core/Makefile
> config.status: creating core/ignite.pc
> config.status: creating jni/include/Makefile
> config.status: creating jni/Makefile
> config.status: creating ignite/Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
> config.status: executing libtool commands
> rm: cannot remove 'core': Is a directory
>
> Does this need some fixing, or am I missing some steps?
>

[Shashank Gandham]

Hi,

If I ignore that and continue with the process of installation with 'make'
command, here is the error I get.

make[3]: Entering directory
'./apache-ignite-1.8.0-src/modules/platforms/cpp/core/include'
make[3]: *** No rule to make target 'ignite/impl/interop/interop_target.h',
needed by 'all-am'.  Stop.
make[3]: Leaving directory
'./apache-ignite-1.8.0-src/modules/platforms/cpp/core/include'
Makefile:697: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
'./apache-ignite-1.8.0-src/modules/platforms/cpp/core'
Makefile:426: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory './apache-ignite-1.8.0-src/modules/platforms/cpp'
Makefile:358: recipe for target 'all' failed
make: *** [all] Error 2

Regards,
Shashank

On Mon, Feb 20, 2017 at 3:39 PM, Igor Sapego <[hidden email]> wrote:

> Hi,
>
> This is not an error. It comes from the Automake buildsystem considers
> files named "core" to be a coredumps and tries to remove them. Ignite C++
> has library named "core" with corresponding directory.
>
> Shortly speaking, just ignore this message.
>
> Best Regards,
> Igor
>
> On Sun, Feb 19, 2017 at 12:45 PM, Shashank Gandham <
> [hidden email]> wrote:
>
> > The ./configure command produces the following error:
> >
> > configure: creating ./config.status
> > config.status: creating Makefile
> > config.status: creating core-test/include/Makefile
> > config.status: creating core-test/Makefile
> > config.status: creating common/os/linux/include/Makefile
> > config.status: creating common/include/Makefile
> > config.status: creating common/Makefile
> > config.status: creating binary/include/Makefile
> > config.status: creating binary/Makefile
> > config.status: creating odbc/include/Makefile
> > config.status: creating odbc/Makefile
> > config.status: creating odbc-test/include/Makefile
> > config.status: creating odbc-test/Makefile
> > config.status: creating core/include/Makefile
> > config.status: creating core/Makefile
> > config.status: creating core/ignite.pc
> > config.status: creating jni/include/Makefile
> > config.status: creating jni/Makefile
> > config.status: creating ignite/Makefile
> > config.status: creating config.h
> > config.status: config.h is unchanged
> > config.status: executing depfiles commands
> > config.status: executing libtool commands
> > rm: cannot remove 'core': Is a directory
> >
> > Does this need some fixing, or am I missing some steps?
> >
>

[Igor Sapego]

Well, this is another issue. It has been fixed already, but still affects
1.8.0 source release.

As a workaround for now you can use sources from Git repository 1.8.0 tag
[1], or you can
only get missing apache-ignite-1.8.0-src/modules/platforms/cpp/core/include/
ignite/impl/interop/interop_target.h
file from there and put it in your sources.

[1] - https://github.com/apache/ignite/releases/tag/1.8.0

Best Regards,
Igor

On Mon, Feb 20, 2017 at 1:33 PM, Shashank Gandham <[hidden email]
> wrote:

> Hi,
>
> If I ignore that and continue with the process of installation with 'make'
> command, here is the error I get.
>
> make[3]: Entering directory
> './apache-ignite-1.8.0-src/modules/platforms/cpp/core/include'
> make[3]: *** No rule to make target 'ignite/impl/interop/interop_
> target.h',
> needed by 'all-am'.  Stop.
> make[3]: Leaving directory
> './apache-ignite-1.8.0-src/modules/platforms/cpp/core/include'
> Makefile:697: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> './apache-ignite-1.8.0-src/modules/platforms/cpp/core'
> Makefile:426: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory './apache-ignite-1.8.0-src/
> modules/platforms/cpp'
> Makefile:358: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Regards,
> Shashank
>
> On Mon, Feb 20, 2017 at 3:39 PM, Igor Sapego <[hidden email]> wrote:
>
> > Hi,
> >
> > This is not an error. It comes from the Automake buildsystem considers
> > files named "core" to be a coredumps and tries to remove them. Ignite C++
> > has library named "core" with corresponding directory.
> >
> > Shortly speaking, just ignore this message.
> >
> > Best Regards,
> > Igor
> >
> > On Sun, Feb 19, 2017 at 12:45 PM, Shashank Gandham <
> > [hidden email]> wrote:
> >
> > > The ./configure command produces the following error:
> > >
> > > configure: creating ./config.status
> > > config.status: creating Makefile
> > > config.status: creating core-test/include/Makefile
> > > config.status: creating core-test/Makefile
> > > config.status: creating common/os/linux/include/Makefile
> > > config.status: creating common/include/Makefile
> > > config.status: creating common/Makefile
> > > config.status: creating binary/include/Makefile
> > > config.status: creating binary/Makefile
> > > config.status: creating odbc/include/Makefile
> > > config.status: creating odbc/Makefile
> > > config.status: creating odbc-test/include/Makefile
> > > config.status: creating odbc-test/Makefile
> > > config.status: creating core/include/Makefile
> > > config.status: creating core/Makefile
> > > config.status: creating core/ignite.pc
> > > config.status: creating jni/include/Makefile
> > > config.status: creating jni/Makefile
> > > config.status: creating ignite/Makefile
> > > config.status: creating config.h
> > > config.status: config.h is unchanged
> > > config.status: executing depfiles commands
> > > config.status: executing libtool commands
> > > rm: cannot remove 'core': Is a directory
> > >
> > > Does this need some fixing, or am I missing some steps?
> > >
> >
>