20 Apr
2012
20 Apr
'12
1:34 a.m.
On 04/19/2012 07:55 PM, Darrell Anderson wrote:
Those imageplugin directories were part of the recent
TQ patches:
http://git.trinitydesktop.org/cgit/digikam/commit/?id=82e857b822ab15a2762a8…
I'm trying to catch up to you so we can compare notes and get this crappola behind
us.
I finally have all of my 32-bit and 64-bit systems installed, two of which have gcc 4.7.
However, I have to run my builds methodcially to control the process with each. If I try
to do all at once then I'll get confused and will be fighting too many problems
concurrently. I hate fighting windmills.
Sort of like shoveling water with a pitchfork :)
Thus far I can build on 32-bit Slackware 13.1 (gcc
4.4.4) and 13.37 (gcc 4.5.2). Today I started polishing my scripts to support 64-bit and
made a dent with Slackware 13.1. As I know 13.1 32-bit builds, I have a barometer for
treading through the 64-bit version.
Hopefully in a few days I'll have made a complete run with all 6 systems. Actually 4
systems. The newest two are gcc 4.7. I expect similar problems as you, but then at least
we will stumble across the failures together and have other systems that are known to
build without serious error.
I really don't think you will find too many. I'm amazed at how quickly the gcc47
and libpng15 dominos fell. What seemed insurmountable 3 weeks ago, seems kind of
easy now. I guess that's the way it goes.
The x86_64 build just completed - ALL GOOD. I don't know what the hell happened
to botch the prefix during the last build. Once I say the i686 build complete
successfully, that really had me scratching my head.
But digikam is FIXED!! Push them patches :)
http://www.3111skyline.com/dl/dt/trinity/ss/digikam-OK.jpg
--
David C. Rankin, J.D.,P.E.
