В сообщении от Суббота 12 января 2008 Marc Espie написал(a):
> On Sat, Jan 12, 2008 at 05:18:58PM +0300, Pereresus ne Vlezaet Buggy wrote:
> > Here are updates to libkdcraw & libkexiv2, which are dependencies
> > to digikam. Nowadays digikam do not even get built because current
> > port lib versions are out of date. (But it's configure script
> > doesn't report this as an error... So I cranked LIB_DEPENDS. All
> > those patches go inline at the end of this letter.
> >
> > Also there is a patch for KDE port that makes patch-ac_include_m4
> > grow, so configure script doesn't say now that c++ linker cannot
> > build shared libraries.
>
> You're not saying which libraries you're talking about.
> This is something that gets solved locally by linking the required
> libraries in kdcraw/digikam.
I'm saying about this line in confgure script output:
checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes
Without additions in patch-ac_include_m4, there will be "no". I dunno
if this is critical or not. I also made port for kopete-otr, which
also builds fine with that patch, and both libs mentiponed above
(kdcraw and kexiv2) builds fine with that patch too. (kopete-otr has
another problem, probably not related to porting at all: it crashes
Kopete first time you try to establish secured session, I think I can
resolve this myself, so not bothering anyone till it's get ready).
> > digikam itself build still fails, now with failures like this:
> >
<...>
>
> Builds here, don't know what's wrong on your system.
Maybe. I'll try fresh install from the newest snapshot this night.
> Probably a side effect of your acinclude.m4 patch...
Don't think so, see above.
> > Also, digiKam building requires that previous requires that previous
> > version is removed from the system is this OK? And, if not, could
> > anyone give a clue where to dig to avoid this behavior?
>
> This is a general problem, this will get solved when we finally switch
> to our own libtool. Don't spend any time trying to work around it,
> it's not worth it.
Thank you for explanation.
> Next time, just look at whomever did the last commit, and send an email,
> okay ?
Sorry, I thought you are too busy to email you privately for such small
troubles. :)
BTW (offtopic), can you say, is anyone working on KDE 4.0 port now?
I understand that it is a big work and myself isn't too clever to tweak it,
but I can (and want) at least test something that is done already. :)
--
WBR,
Pereresus ne Vlezaet Buggy
