← Back to team overview

maria-discuss team mailing list archive

Re: mariadb-connector-c mariadb_config: Faulty output with static gssapi plugin

 


> Am 2018-01-08 um 14:02 schrieb Sergei Golubchik <serg@xxxxxxxxxxx>:
> 
> Hi, Stefan!
> 
> Thanks! Reported as https://jira.mariadb.org/browse/CONC-303
> and fixed at once

This is my favourite reaction to issues in OSS.

Thank you very, very much! :-)

Stefan

> 
> On Jan 05, Stefan Scherfke wrote:
>> Hi all,
>> 
>> the output of "mariadb_config --libs[_r]" is faulty if the AUTH_GSSAPI
>> plugin is configured as static:
>> 
>> I built mariadb-connector-c 3.0.2 on Fedora 26 with this command:
>> 
>>   mkdir build
>>   cd build
>>   cmake -DAUTH_GSSAPI=STATIC ..
>>   make
>> 
>> The output of "mariadb_config" then looks like this:
>> 
>>   $ mariadb_config/mariadb_config --libs_r
>>   -L/usr/local/lib/mariadb/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto -l-lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err
>> 
>> All libs should be named like "-l<name>" but gssapi_krb5 has a double
>> "-l-l" prefix.
>> 
>> This problems becomes more apparent when I build mariadb-connector-c as
>> a Python Conda package.
>> 
>> Without the "AUTH_GSSAPI=STATIC" flag, I get the following libs:
>> 
>>   -L/opt/emsconda/conda-bld/mariadb-connector-c/env/lib/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto
>> 
>> With the "AUTH_GSSAPI=STATIC" flag, I get the following libs:
>> 
>>   -L/opt/emsconda/conda-bld/mariadb-connector-c/env/lib/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto -l-L/opt/emsconda/conda-bld/mariadb-connector-c/envplaceho/lib -Wl,--enable-new-dtags -Wl,-rpath -Wl,/opt/emsconda/conda-bld/mariadb-connector-c/envplaceho/lib -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err
>> 
>> The problematic part there is the "-l-L/opt/emsconda/.../lib" part which
>> confuses other tools like Mydumper when they are compiled against
>> mariadb-connector-c.
>> 
>> Is this an issue with mariadb-connector-c or can I fix it in my build
>> process somehow?
>> 
> Regards,
> Sergei
> Chief Architect MariaDB
> and security@xxxxxxxxxxx



References