The patch above that Michael referred to appeared to not work last
night. I will likely end up having to upload my new version of OOo
(1:3.2.0-6ubuntu1) with the patch he couldn't get to work and see if it
has any better luck on the buildds as Final Freeze is tomorrow.
--
openoffice.org FTBFS on
This bug was fixed in the package openoffice.org - 1:3.2.0-7ubuntu1
---
openoffice.org (1:3.2.0-7ubuntu1) lucid; urgency=low
* Resynchronise with Debian (r1940). Remaining changes:
- Add Launchpad integration support.
- Add Launchpad translations support.
- Add package
Looking at buildd logs, we're now 8 hours out of 48-72 hours of build
time, and well past the initial point of breakage with OOo. Seems we're
worked around the problem.
--
openoffice.org FTBFS on armel
https://bugs.launchpad.net/bugs/555977
You received this bug notification because you are a
@Dave Martin, no core dump is recorded. I posted the backtrace
available, but the debugger is choking on something. Problem is NOT with
UNO (at least directly), seems only i18ntools in the source is effected.
I don't want to selectively change optimizations, because that may
introduce subtile bugs
The reasoning behind my suggestion is that OOo is vast - probably the
biggest single app we're dealing with, so we really want to keep Thumb-2
here.
However, I agree with you in the short term— we want to fix the real
problem rather than chase random non-issues caused by a nonstandard
build
@dmat: no, it happens on all hardware (Dove, imx51), I get no core dump
on my system when the segfault happens. We can SRU OOo to remove the
-marm option when we finally fix it properly since its a kludge to get
OOo for release. We're about to reach final freeze, so I don't think
we're going to
gdb may be failing to produce a backtrace due to missing debug
symbols--- make sure you have the debug symbols for all of OOo's
dependencies installed.
Due to amount of time required to build OOo I suggest to go with the ARM
build if we have no clue about how to fix the bug.
Can we build just
building some subprojects with other optimization options is possible.
see ooo-build/patches/dev300/ubuntu-arm-thumb.diff how this can be done.
--
openoffice.org FTBFS on armel
https://bugs.launchpad.net/bugs/555977
You received this bug notification because you are a member of Ubuntu
Bugs,
bridges/source/cpp_uno/{shared,gcc3_linux_arm}/makefile.mk would be
candidates for
+.IF $(CPUNAME)==ARM
+CFLAGS += -marm
+.ENDIF
--
openoffice.org FTBFS on armel
https://bugs.launchpad.net/bugs/555977
You received this bug notification because you are a member of Ubuntu
Bugs, which is
gdb may be failing to produce a backtrace due to missing debug symbols---
make sure you have the debug symbols for all of OOo's dependencies installed.
Doesn't seem to be the issue here, first because the stack points to an
address within an object belonging to the OOo source, and second
You may be right, but I recommend having all the debug symbols installed
anyway. Not having them is asking for trouble right now (though work is
ongoing in gdb to improve backtracing)
@Michael, is there a way I can get your debug binaries and a core dump?
--
openoffice.org FTBFS on armel
Doing more test builds, building with -marm makes the segfault with
i18npool disappear (and presumably would let the build finish). Given
our proximity to final freeze, I think this is an acceptable workaround
and then we can properly solve it for 10.10. Any objections?
--
openoffice.org FTBFS
With a patched gdb, I managed to get a backtrace, but its of limited
use, the stack seems fairly corrupted:
mcasadev...@dawn:~/src/ooo/current/openoffice.org-3.2.0/build/i18npool/source/localedata/data$
** Changed in: openoffice.org (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-2 = ubuntu-10.04
--
openoffice.org FTBFS on armel
https://bugs.launchpad.net/bugs/555977
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I did a test build of the lastest archive version on a dove board just
to completely rule out the hardware. It segfaulted so this isn't a
hardware issue. I also ran a parallel build of ubuntu1 on an imx51 build
which also failed; the change that broke OOo appears toolchain related.
--
** Tags added: armel
--
openoffice.org FTBFS on armel
https://bugs.launchpad.net/bugs/555977
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I was able to reproduce this build failure of jocote after two hours of
building. I want to retry on a Dove based board in case the failure is
actually a problem common to the entire imx51 family, but this looks
like a legit bug; It appears saxparser is segfaulitng versus bash, but I
still don't
Adding link to patch of what changed between the working and failing
build of OOo.
http://launchpadlibrarian.net/42029557/openoffice.org_1%3A3.2.0-4ubuntu1_1%3A3.2.0-4ubuntu2.diff.gz
It built properly on jambul, but with the diff above then failed on
jambul and huito (maybe others as it was
Here's what gdb gives for a backtrace:
(gdb) bt
#0 0x401d5596 in calculate ()
from
/home/vorlon/openoffice.org-3.2.0/ooo-build-3-2-0-7/build/OOO320_m12/solver/320/unxlngr.pro/lib/libuno_cppu.so.3
#1 0x401d2da4 in ?? ()
from
Also note that it doesn't look like anything relevant changed between
the version that last built properly on arm and the subsequent ones that
did not build. I may of course be wrong, but this seems like a buildd
issue of some sort.
--
openoffice.org FTBFS on armel
20 matches
Mail list logo
