Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 10.1.8
-
Fix Version/s: N/A
-
Component/s: Compiling, Storage Engine - Mroonga
-
Labels:None
-
Environment:Linux
-
Sprint:10.1.9-3
Description
When building mariadb with -DPLUGIN_MROONGA=NO, libgroonga is still built:
[ 84%] Built target innobase
|
make[4]: Entering directory `/home/build/p4/zimbra/main/ThirdParty/mariadb/tmp/UBUNTU14_64/zimbra-mariadb'
|
Scanning dependencies of target libgroonga
|
make[4]: Leaving directory `/home/build/p4/zimbra/main/ThirdParty/mariadb/tmp/UBUNTU14_64/zimbra-mariadb'
|
make[4]: Entering directory `/home/build/p4/zimbra/main/ThirdParty/mariadb/tmp/UBUNTU14_64/zimbra-mariadb'
|
[ 84%] Building C object storage/mroonga/vendor/groonga/lib/CMakeFiles/libgroonga.dir/com.c.o
|
[ 84%] Building C object storage/mroonga/vendor/groonga/lib/CMakeFiles/libgroonga.dir/command.c.o
|
(etc)
This is incorrect, since MROONGA is not enabled.
Attachments
Issue Links
- is duplicated by
-
MDEV-8969 groonga is compiled even with -DPLUGIN_MROONGA=NO
-
- Closed
-