Ganglia largely assumes SunRPC support in glibc. It would be be beneficial to support another implementation since the glibc implementation is deprecated and doesn't support things like IPv6.
It's possible to build Ganglia with an alternate SunRPC implementation by passing the LIBS/CPPFLAGS to configure. However, there is currently no way to get the additional include path(s) into ganglia-config for anything that wants to build against libganglia.
Regardless, it looks like ganglia-config --include should support --all to behave like --libs, returning all include paths required by ganglia headers (including those for apr and confuse).
I see that --cflags which does include additional include paths but this also means consuming all CFLAGS from ganglia, including optimization, debugging, etc flags. ganglia-config probably shouldn't return these extra flags, only the flags necessary for building against ganglia.
Ganglia largely assumes SunRPC support in glibc. It would be be beneficial to support another implementation since the glibc implementation is deprecated and doesn't support things like IPv6.
It's possible to build Ganglia with an alternate SunRPC implementation by passing the LIBS/CPPFLAGS to configure.
However, there is currently no way to get the additional include path(s) into ganglia-config for anything that wants to build against libganglia.Regardless, it looks like ganglia-config --include should support --all to behave like --libs, returning all include paths required by ganglia headers (including those for apr and confuse).I see that --cflags which does include additional include paths but this also means consuming all CFLAGS from ganglia, including optimization, debugging, etc flags. ganglia-config probably shouldn't return these extra flags, only the flags necessary for building against ganglia.