On 5. 4. 2013 Ryan McCoskrie wrote:
> Could someone please explain why each time I try setting CMAKE_CXX_COMPILER
> distcc, cmake then tells outputs:
> > CMake Error at CMakeLists.txt:34 (message):
> > TagLib does not have ASF support compiled in.
>
> I've gone so far as to compile and install my own copies of taglib (1.8 and
> 1.7 for sake of comparison) and I always get this error.
Hmm, we use try-compile check to test presence of the ASF support in TagLib. I
see a couple of possible reasons (I haven't verified plausibility of any of
them):
a) distcc depends on the fact that you call it with the correct name alias,
i.e. that you should set CMAKE_CXX_COMPILER to something like
/usr/lib/distcc/g++; even better, cmake should pick up it automatically if you
prepend something line /usr/lib/distcc to $PATH and remove CMakeCache.txt
b) distcc assumes that all hosts have the same system-wide headers. In that
case it may be needed for you to install the same TagLib version on all
building hosts
c) our try-compile check is simply broken if you set CMAKE_CXX_COMPILER to
something it doesn't expect.
d) our try-compile check is broken in a way that it uses the system-wide
TagLib even if you specified your self-compiled; this is not likely the cause
as I think that even TagLib 1.7 ships with ASF support by default.
Regards,
Matěj
_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok
