ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Luo (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-12022) Compilation bug possibly introduced by IGNITE-1472 (commit 43e3fee)
Date Sun, 28 Jul 2019 20:53:00 GMT
Jack Luo created IGNITE-12022:
---------------------------------

             Summary: Compilation bug possibly introduced by IGNITE-1472 (commit 43e3fee)
                 Key: IGNITE-12022
                 URL: https://issues.apache.org/jira/browse/IGNITE-12022
             Project: Ignite
          Issue Type: Bug
          Components: binary, build, thin client
    Affects Versions: 2.8
         Environment: Reproduction steps 

# Step 1 - sparse clone the thin-client from master
cd /tmp
mkdir ignite
cd ignite
git init
git config core.sparseCheckout true
git remote add origin https://github.com/apache/ignite.git
echo "modules/platforms/cpp/" > .git/info/sparse-checkout
git fetch --depth 1 origin
git checkout master

# Step 2 - make and install static and shared libraries
cd modules/platforms/cpp/
libtoolize && aclocal && autoheader && automake --add-missing &&
autoreconf
./configure --disable-node --disable-odbc
make -j$num_cpus
make install
            Reporter: Jack Luo


IGNITE-1472 introduced ignite/binary/binary_enum_entry.h and ignite/binary/binary_enum.h.
These header files are used inside ignite/impl/binary/binary_utils.h:30:10. 

However, after compilation using 

./configure --disable-node --disable-odbc

the header files are not installed under /usr/local/include/ignite/binary/ thus causing compilation
error in user program. 

 

The fix is to copy the two files to /usr/local/include/ignite/binary.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message