20 Dec
2013
20 Dec
'13
4:47 p.m.
You could reference e.g. gentoo bugzillaand other:
https://bugs.gentoo.org/show_bug.cgi?id=490194
It's resolved here so I haven't
The trinity is not the only project that is affected the gentoo
also mentions ldc(d compiller) and openvas.
Consider this: KDE is completely cmake based. Slackware 14.1 comes
with cmake 2.8.12.0. All of the KDE packages compiled for the
official Slackware 14.1 release. I'm assuming without these
problems. Convincing the Slackware maintainer that cmake 2.8.12.0
is problematic needs a good explanation.
That KDE compiled without failure and Trinity does not compile
leads to an obvious question of what are the Trinity folks doing
"wrong" that the KDE folks are doing "right"?
Right now I don't understand the issues involved. I'm not a
developer or coder. I'm a packager and tester who is devoted to
keeping Trinity alive. These cmake problems are above and beyond my
full understanding. I can't ask the Slackware maintainer to update
to cmake 2.8.12.1 "just because." Trinity is not "officially"
supported in any distro. Emphasis on "officially." Asking distro
maintainers to update cmake needs a clear explanation --- something
I am not able to do. Somebody who understands the details of all of
these problems could write something that I could forward to the
Slackware maintainer.
That said, as I reported in a previous post, I still can't build
Trinity after I updated to 2.8.12.1 on my own. :-)
Darrell