Re: kde4 on debian arm && armel
On Wed, Dec 19, 2007 at 02:21:20PM +0000, Sune Vuorela wrote:
> On 2007-12-19, Martin Guy <martinwguy@yahoo.it> wrote:
> > 2007/12/19, Sune Vuorela <nospam@vuorela.dk>:
> >> kde4 release candidates are in experimental. The experimental arm buildd
> >> seems to fail to build with some weild errors from libstdc++
> >>
> >> If someone with a bit more clue than me could try look at the arm build
> >> failure - and someone with spare armel cpu power could try launch a
> >> kde4libs build it would be very nice.
> >
> > you are welcome to use the 600MHz 512MB box here via ssh If armel sid
> > is recent enough for you to test it. Mail me privately if so.
>
> It should be. kde4libs builds with stuff from unstable. I am mailing you
> private about it.
>
> > However, from the log it seems to have other problems. I spotted:
> >
> > "Default version of libsoprano-dev not sufficient, no suitable version found."
>
> which version of soprano is used ? Newest one seems to be b uilt on
> armel 2 days ago.
>
> >
> > and
> >
> > "dpkg-source: applying /org/buildd/build/kde4libs_3.97.0-2.diff.gz
> > Condition for **LTCONFIG-BIG-ENDIAN-FIX patch ok
> > Applying **LTCONFIG-BIG-ENDIAN-FIX patch
> > The text leading up to this was:
> > --------------------------
> >|--- x/ltconfig~ Fri Jun 4 14:14:04 1999
> >|+++ x/ltconfig Fri Jun 4 14:14:14 1999
> > --------------------------
> > No file to patch. Skipping patch.
> > 1 out of 1 hunk ignored"
>
> I don't see this anywhere in the kde4libs sources
That's because it's not part of the kde4libs sources. This is a rarely
used feature of sbuild which allows one to conditionally apply patches
over all sources -- in this case it tries to update ltconfig. However,
the patch seems outdated.
I don't think it's your problem to fix this; whoever wrote that patch
should update it. Moreover, since it says "BIG-ENDIAN", I don't think
you should worry about it for your arm*el* build...
--
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22
Reply to: