Re: Development version of BIND 9 - 9.21.10 with meson build system

Uh oh, I wrote this before I checked the meson.build:

We actually should have the workaround in meson too:

## userspace-rcu
urcu_dep = [dependency('liburcu-cds', version: '>=0.10.0')]
if rcu_flavor == 'membarrier'
    config.set('RCU_MEMBARRIER', true)
    urcu_dep += dependency('liburcu', version: '>=0.10.0')
elif not developer_mode
    error('Changing Userspace-RCU flavor is allowed only in development mode')
elif rcu_flavor == 'bp'
    config.set('RCU_BP', true)
    urcu_dep += dependency('liburcu-bp', version: '>=0.10.0')
elif rcu_flavor == 'mb'
    config.set('RCU_MB', true)
    urcu_dep += dependency('liburcu-mb', version: '>=0.10.0')
elif rcu_flavor == 'qsbr'
    config.set('RCU_QSBR', true)
    urcu_dep += dependency('liburcu-qsbr', version: '>=0.10.0')
endif

# liburcu << v0.13.0 didn't add -lurcu-common and some toolchains would
# not add it automatically - we need to add it explicitly in such case.

if urcu_dep[1].version().version_compare('<0.13.0')
    urcu_dep += cc.find_library('liburcu-common')
endif

But I am guessing your problem is platform specific - so I would still
suggest to bump the urcu version to 0.15.3 and be done with that.

--
Ondřej Surý (He/Him)
[email protected]

My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.

> On 3. 9. 2025, at 14:56, Ondřej Surý <[email protected]> wrote:
> 
> Well, we had this workaround for urcu << 0.13 in configure.ac,
> but I would suggest that you should rather use the latest urcu
> release instead of adding the workaround back to meson.build.
> 
> Ondrej
> --
> Ondřej Surý (He/Him)
> [email protected]
> 
> My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.
> 
>> On 3. 9. 2025, at 14:53, Havard Eidnes via bind-users <[email protected]> wrote:
>> 
>>> Does
>>> https://bind9.readthedocs.io/en/latest/chapter10.html#building-bind-9
>>> help?
>> 
>> Yes, it gets me a bit further.
>> 
>> The current stumbling block is that the configury system can't
>> find liburcu-common (despite finding the other rcu libs),
>> seemingly that's because the pkg-config file for that library is
>> somehow "missing" from the package I'm using (based on rcu
>> version 0.12.1).  I'm going to follow that lead further.
>> 
>> That said, I would still claim it's a good idea and probably also
>> cheap to have the build hints in e.g. a short INSTALL.md file in
>> the top directory in the source distribution, pointing to the
>> more full description via a URL and/or a file pointer.  Just a
>> suggestion to make life easier for folks who are coming from a
>> similar position as myself (I'm guessing I'm not alone).
>> 
>> Regards,
>> 
>> - Håvard
>> -- 
>> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
> 

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.