[MDEV-8677] mroonga storage engine fails to find LZ4 Created: 2015-08-26  Updated: 2015-08-30  Resolved: 2015-08-30

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Mroonga
Affects Version/s: 10.0.21
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Brad Smith Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

OpenBSD


 Description   

Trying to build the Mroonga storage engine with MariaDB 10.0.21 CMake is able to detect the presence of LZ4 but it doesn't use the header path (from the pkg-config file) to find the header (and make sure to use the library path when linking)thus the build fails...

/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1231:17: warning: lz4.h: No such file or directory
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c: In function 'grn_ja_ref_lz4':
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1255: warning: implicit declaration of function 'LZ4_decompress_safe'
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c: In function 'grn_ja_put_lz4':
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1378: error: 'LZ4_MAX_INPUT_SIZE' undeclared (first use in this function)
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1378: error: (Each undeclared identifier is reported only once
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1378: error: for each function it appears in.)
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1385: warning: implicit declaration of function 'LZ4_compressBound'
 
/home/ports/pobj/mariadb-10.0.21/mariadb-10.0.21/storage/mroonga/vendor/groonga/lib/store.c:1391: warning: implicit declaration of function 'LZ4_compress'



 Comments   
Comment by Elena Stepanova [ 2015-08-29 ]

Please provide your liblz4.pc file.

Comment by Brad Smith [ 2015-08-30 ]

Thanks for the hint. My bad for the noise. Looking at the pkg-config file it turns out due to an issue with the build infrastructure the resulting package for LZ4 had completely bogus paths in the pkg-config file pointing to the build directory instead of the destination installation path.

Generated at Thu Feb 08 07:28:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.