[PATCH] build: have a disable-static build succeed

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Jan Engelhardt jengelh at inai.de
Wed Sep 16 16:48:02 UTC 2015


On Wednesday 2015-09-16 18:11, Holger Freyther wrote:
>> On 16 Sep 2015, at 14:32, Jan Engelhardt <jengelh at inai.de> wrote:
>> 
>> When using configure --disable-static, no libosmogsm.a will be
>> created, and the tests fail to link because symbols like _a5_3 and
>> _a5_4 are not exported through the only remaining libosmogsm.so.
>> 
>> A method to overcome this is an intermediate private non-distributed
>> library, examples of which are present in e.g. libabc, kmod and
>> systemd.
>> 
>> With this, disable-static can now be the default and practical compile
>> time be halved.
>
>thanks. What is the likelihood of —disable-static build to fail?

No different from before.

>Does it make sense to add a jenkins config/matrix for this?

An extra one no; just modify the existing job and let it use 
`./configure --enable-static` which will build all variants.



More information about the OpenBSC mailing list