Message: previous - next
Month: April 2012

Re: [trinity-devel] BAD New [was Re: [trinity-devel] UPDATED patch ...SOLVED: digikam libpng15 ...]]

From: Darrell Anderson <humanreadable@...>
Date: Thu, 19 Apr 2012 17:18:04 -0700 (PDT)
> I think this patch probably broke it (however, I don't know
> which part):

That would be this patch:

I haven't had any problems with the patch.

Digikam builds here without error --- although I'm not fighting the windmills of gcc 4.7. I have built digikam against both gcc 4.4.4 (Slackware 13.1) and 4.5.2 (Slackware 13.37).

You mentioned previously about digikam not creating a new database. That was happening to me several days ago until I scrubbed digikam of inadvertent TQ changes. That problem disappeared thereafter.

Have you pulled the latest digikam sources?

There are so many patches being uploaded to GIT that every couple of days I stop trying to build individual packages and start my build sequence from scratch. When I want to focus on one package, I"m careful not to pull the new source tree because often that means no less than building tdelibs and tdebase over, often TQt3 too, which often affects everything else.

That patch could be the culprit, but if there were problems with that patch then everything built with automake would be affected.