Sergei,
Thanks a lot for investigating this. I looked at the armel failure over
Christmas and saw that it was a failure to build docs. Looks like sparc is
the same. I have an arm machine at home and I am now firing it up so that I
can investigate further.
I can believe the powerpc failure is
Hi Kevin,
On Sat, Jan 11, 2014 at 9:12 PM, Kevin Glynn kevin.gl...@gmail.com wrote:
I can believe the powerpc failure is due to a missing pattern in OZPLATFORM
but how do you see that in the build logs? I see the failure to find
libDSS.a which is because we built a libDSS.so instead. I need
Oh yes, I see that now. I'm surprised it got as far as it did with that
wrong, but I'll fix and we can see what happens then.
On Sat, Jan 11, 2014 at 6:18 PM, Sergei Golovan sgolo...@nes.ru wrote:
Hi Kevin,
On Sat, Jan 11, 2014 at 9:12 PM, Kevin Glynn kevin.gl...@gmail.com
wrote:
I can
Hi Niels and Kevin,
As far as I can see from build logs, there are two build problems with
Mozart currently:
1) on powerpc the correct architecture is failed to be determined,
because there's the following pattern in share/bin/ozplatform to do
that: ppc\ Linux\ 2.* (which doesn't match the
Package: mozart
Version: 1.4.0-8.1
Severity: serious
Hi Kevin and Sergei,
mozart/1.4.0-8.1 FTBFS on armel, kfreebsd-i386, powerpc and sparc.
However, previous version built there, so this failure blocks testing
migration (and therefore keeps the fix for #726030 out of testing).
NB: The state of
5 matches
Mail list logo
