trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: January 2012

Re: [trinity-users] kaffeine-3.5.13 compilation error

From: "roman" <lists@...>
Date: Sun, 29 Jan 2012 15:40:16 +0100
Hey,

On Sun, January 29, 2012 15:16, E. Liddell wrote:
> On Sun, 29 Jan 2012 13:48:12 +0100
> "roman" <lists@...> wrote:
>
>> Hi,
>>
>> On Sat, January 28, 2012 03:39, E. Liddell wrote:
>> > None of the kde-sunset ebuilds work for Trinity unchanged--the
>> tarballs
>> > don't have quite the same structure, which screws up the eclasses.
>> >
>> > Anyway, hopefully all the attachments will come through--there should
>> be
>> > one ebuild and two supporting eclasses which are similar but not
>> identical
>> > to the corresponding eclasses from kde-sunset.  Keep in mind that I've
>> > only compiled this with all use flags off in a test environment that
>> has
>> > only
>> > had Trinity installed to it, and never any version of KDE.  Hopefully
>> > it'll work for you.
>>
>> Thx for the ebuild/eclass, but sadly it didn't work for me. I know the
>> kde-sunset ebuilds quite well (and that they do not work). I have
>> updated
>> some of those myself. But with the chanke to trinity/cmake i am still a
>> little lost. I have taken the ebuilds provided by serghei and started
>> editing/updating them for the 3.5.13 release version. I currently do
>> have
>> a gtk-desktop without any qt/kde installed. I guess i will have to
>> recheck
>> the other ebuilds for kdelibs/startkde again for errors.
>
> ::muttermumblecurse::  Did the ebuild fail in the same way as the direct
> build, or was it a different failure?  I'd like to figure out what's going
> on
> and get the thing working reliably if it's within my ability to do so,
> although
> working with this stuff often makes me feel like I'm banging my head
> against a wall.
>
> We need some sort of organized effort to package Trinity for Gentoo--it
> seems like 4-5 people have intermittently tried to do bits and pieces,
> with
> no real coordination beyond copying Serghei's initial ebuilds, and likely
> some duplication of effort.

You are right about the organized effort. The eclasses alone seem to be
quite messy.. The ebuild also came down to the following error which seems
to be an code-error?

kxinewidget.cpp:2641:66: error: invalid conversion from ‘const char*
const*’ to ‘char**’ [-fpermissive]

--