[avahi] Avahi/0.8: Static build doesn't work

[garethsb]

By default, my application built with the avahi/0.8 package d9df2dae7794b8bdde633c215e6123c686ecc867, downloaded from CCI. The build worked fine. However, when running the app, the Avahi APIs report errors. When I forced conan install to rebuild the same package locally, the APIs work successfully.

I also tried adding the option avahi:shared=True to my app to test the package 23c72e9789f13b684d267c26ce0b33d0e9e40b8b, downloaded from CCI (not built locally). That works successfully too.

I'm not sure how to investigate why the static build from CCI doesn't work on my system.

Package and Environment Details

• Package Name/Version: avahi/0.8
• Operating System+version: Linux Ubuntu 20.04
• Compiler+version: GCC 10
• Conan version: conan 1.41.0
• Python version: Python 3.8.10

Conan profile (output of conan profile show default)

[settings]
os=Linux
os_build=Linux
arch=x86_64
arch_build=x86_64
compiler=gcc
compiler.version=9
compiler.libcxx=libstdc++
build_type=Release
[options]
[conf]
[build_requires]
[env]

That shows GCC 9, but I'm building from CMake which shows:

-- Conan: Automatic detection of conan settings from cmake
-- Conan: Settings= -s;build_type=Release;-s;compiler=gcc;-s;compiler.version=10;-s;compiler.libcxx=libstdc++11

[garethsb]

Unfortunately, the test package for avahi/0.8 is very minimal (mea culpa!) so we can't tell from C3I test logs whether the library actually worked there, because the API that gets called will return the same error I'm seeing (-65537) anyway, simply because the test package doesn't start up avahi-daemon.

[garethsb]

Just tracking this has just reoccurred for us with an application built using the latest avahi/0.8 package, run on Ubuntu 20.04.5 LTS which has avahi-daemon (0.7) installed by system package manager. Investigating...

cc: @adanos911