-
Notifications
You must be signed in to change notification settings - Fork 0
Cannot build tuple-keydef with Tarantool 2.10.3-0-g8aca8a1 #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Likely the root of the problem is the same as in tarantool/kafka#89. |
Not Mac OS specific, reproduced on Linux. |
Caused by tarantool/tarantool#7663 (a modification of |
|
An inclusion of `string.h` header file was removed from `tarantool/module.h` in tarantool 2.10.3, see [1]. This module uses `strstr()`, `strlen()` and `memcpy()` functions defined by `string.h`, so it must include this header. [1]: tarantool/tarantool#7663 Fixes #24
The new CI rule ensures that a usual developer build flow is working. It also improves testing by using the `Debug` build type, which adds the `-Werror` compiler option. Compiler warnings are interpreted as errors in this case. It is inspired by #24, where the `Debug` build fails, but `RelWithDebInfo` is fine. This commit follows a spirit of [1], where it was declared that we should verify as developer's flow as well as user's flow. We missed developer's flow in CI of this module and now it is here. [1]: tarantool/tarantool#6056
The new CI rule ensures that a usual developer build flow is working. It also improves testing by using the `Debug` build type, which adds the `-Werror` compiler option. Compiler warnings are interpreted as errors in this case. It is inspired by #24, where the `Debug` build fails, but `RelWithDebInfo` is fine. This commit follows a spirit of [1], where it was declared that we should verify as developer's flow as well as user's flow. We missed developer's flow in CI of this module and now it is here. [1]: tarantool/tarantool#6056
The new CI rule ensures that a usual developer build flow is working. It also improves testing by using the `Debug` build type, which adds the `-Werror` compiler option. Compiler warnings are interpreted as errors in this case. It is inspired by #24, where the `Debug` build fails, but `RelWithDebInfo` is fine. This commit follows a spirit of [1], where it was declared that we should verify as developer's flow as well as user's flow. We missed developer's flow in CI of this module and now it is here. [1]: tarantool/tarantool#6056
An inclusion of `string.h` header file was removed from `tarantool/module.h` in tarantool 2.10.3, see [1]. This module uses `strstr()`, `strlen()` and `memcpy()` functions defined by `string.h`, so it must include this header. The problem affects the `Debug` build type, which is default for the `cmake . && make` build flow (it is usually used by developers of the module). This build type adds `-Werror` compilation flag. However the problem doesn't affect the `tarantoolctl rocks install tuple-keydef [<version>]` build flow, because it uses the `RelWithDebInfo` build type. All compiler warnings are just warnings here. [1]: tarantool/tarantool#7663 Fixes #24
An inclusion of `string.h` header file was removed from `tarantool/module.h` in tarantool 2.10.3, see [1]. This module uses `strstr()`, `strlen()` and `memcpy()` functions defined by `string.h`, so it must include this header. The problem affects the `Debug` build type, which is default for the `cmake . && make` build flow (it is usually used by developers of the module). This build type adds `-Werror` compilation flag. However the problem doesn't affect the `tarantoolctl rocks install tuple-keydef [<version>]` build flow, because it uses the `RelWithDebInfo` build type. All compiler warnings are just warnings here. [1]: tarantool/tarantool#7663 Fixes #24
The new CI rule ensures that a usual developer build flow is working. It also improves testing by using the `Debug` build type, which adds the `-Werror` compiler option. Compiler warnings are interpreted as errors in this case. It is inspired by #24, where the `Debug` build fails, but `RelWithDebInfo` is fine. This commit follows a spirit of [1], where it was declared that we should verify as developer's flow as well as user's flow. We missed developer's flow in CI of this module and now it is here. [1]: tarantool/tarantool#6056
The new CI rule ensures that a usual developer build flow is working. It also improves testing by using the `Debug` build type, which adds the `-Werror` compiler option. Compiler warnings are interpreted as errors in this case. It is inspired by #24, where the `Debug` build fails, but `RelWithDebInfo` is fine. This commit follows a spirit of [1], where it was declared that we should verify as developer's flow as well as user's flow. We missed developer's flow in CI of this module and now it is here. [1]: tarantool/tarantool#6056
Environment:
Tarantool:
Steps to reproduce:
cmake . make
Expected result:
Build is successful.
Actual result:
The text was updated successfully, but these errors were encountered: