** Changed in: openoffice.org (Ubuntu Karmic)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/417009
Title:
all openoffice apps die in
** Changed in: openoffice
Status: In Progress = Fix Released
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: openoffice
Status: Fix Released = In Progress
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: openoffice
Status: In Progress = Fix Released
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: openoffice.org (Ubuntu Karmic)
Status: In Progress = Triaged
** Changed in: openoffice.org (Ubuntu Karmic)
Assignee: Matthias Klose (doko) = (unassigned)
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
Is this bug fixed now? I noticed that it built fine on armel after it
was retried.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
checked on current lucid. starting oowriter and working with it works
** Changed in: openoffice.org (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
while the old jaunty copy isn't installed anymore, the copyright still
refers to it.
** Changed in: openoffice.org (Ubuntu Lucid)
Status: Fix Released = In Progress
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
Matthias,
Can you quote the part and what file it is in? I thought I removed it
and I can't find it myself when looking for it just now.
Also for some reason the first time OOo 4ubuntu1 was attempted it failed
and then it passed on retry. I didn't get to see how it failed, but when
trying
Marking back as Fix Released since Matthias says he sees the copyright
change now. I'm not sure why it wasn't showing up for him before.
** Changed in: openoffice.org (Ubuntu Lucid)
Status: In Progress = Fix Released
--
all openoffice apps die in
If this same patch works for Karmic I can prepare a SRU. I have another
unrelated fix that should go into a SRU as well.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug
@Chris: would love seeing it fixed in SRU, but please don't SRU oo.o
just for that, it's a very high load on the archive/mirrors.
If another SRU is pending, fixing this armel uglyness would be very
welcome! :-)
--
all openoffice apps die in
Note that oo.o failed to build on armel
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Michael,
The latest patch that you sent me which is in ooo-build went into the
build uploaded today. Let me know if you have any new patches to add, I
will be doing another upload in the next week before Beta 2 freeze and
could add it then.
Thanks,
Chris
--
all openoffice apps die in
there seem to be still problems (quote from the debian maintainer):
but I fear the change broke extensions:
Enabling: Presentation Minimizer
Enabling: SunPresentationMinimizer.xcs
Enabling: SunPresentationMinimizer.uno.so
ERROR: (com.sun.star.deployment.DeploymentException) { { Message = An
@NCommander, can you confirm that the patch merged in ooo-build was this
one http://pastebin.ubuntu.com/395620/ ? The patch in post #72 would
likely barf on functions with more than 4 args.
Is there a debdiff or equivalent somewhere I can take a look at?
--
all openoffice apps die in
Dave Martin: Talked with _rene_ (OOo maintainer for Debian), and he
confirms that its a problem on Debian with the latest patch but I
couldn't reproduce on Ubuntu off a self-built tree. Will investigate
further, but the patch should be up to date in git.
--
all openoffice apps die in
New patch tested and commited in ooo-build. Just need an upload now.
** Changed in: openoffice.org (Ubuntu Lucid)
Assignee: Michael Casadevall (mcasadevall) = Chris Cheney (ccheney)
** Changed in: openoffice.org (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
all openoffice
Mandriva's Arnaud Patard proposed the following function body to me on IRC:
@
@ Written by Peter Naulls pe...@chocky.org
@ Modified by Caolan McNamara caol...@redhat.com
.file armhelper.s
.text
.align 4
.global privateSnippetExecutor
.type
NCommander gave me the patch at http://pastebin.ubuntu.com/395620/ and
it's working here too.
** Patch added: fix_ooo_arm.patch
http://launchpadlibrarian.net/41027177/fix_ooo_arm.patch
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
** Tags added: patch
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The patch on http://pastebin.ubuntu.com/395620/ is probably the one to
go for, since it preserves 64-bit stack alignment and will work for
target functions which take more than 4 arguments including this (they
end up in a contiguous slab on the stack).
The exception unwinder is also told not to
Unfortunately, we took a look at this again and the fix is obviously
wrong: some arguments are pushed on the stack by privateSnippetExecutor
but never removed; this is almost certain to lead to incorrect
behaviour.
It looks like unwind support is needed for this after all.
--
all openoffice
** Changed in: openoffice.org (Ubuntu Lucid)
Status: Fix Committed = In Progress
** Changed in: openoffice.org (Ubuntu Lucid)
Assignee: Chris Cheney (ccheney) = Michael Casadevall (mcasadevall)
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on
** Changed in: openoffice.org (Ubuntu Karmic)
Status: Won't Fix = In Progress
** Changed in: openoffice.org (Ubuntu Karmic)
Milestone: ubuntu-9.10 = karmic-updates
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
Patch is in ooo-build, and should be in the next OOo upload. Marking fix
commited for Lucid.
** Changed in: openoffice.org (Ubuntu Lucid)
Status: Confirmed = Fix Committed
** Changed in: openoffice.org (Ubuntu Lucid)
Assignee: Michael Casadevall (mcasadevall) = Chris Cheney (ccheney)
ARM folks came up with this patch which seems to fix the issue:
--- armhelper.s 2007-12-12 15:35:44.0 +
+++ armhelper.s 2010-03-11 16:22:29.0 +
@@ -10,13 +10,5 @@
privateSnippetExecutor:
stmfd sp!, {r0-r3} @ follow other parameters on stack
mov
Posting output from some investigations yesterday
-Original Message-
From: Matthew Gretton-Dann
[...]
After some work with NCommander on IRC yesterday afternoon we
identified a problem with privateSnippetExecutor being marked
CANTUNWIND.
Examination of the source shows that this
After yesterdays discussions on determining the CANTUNWIND status of
parts of the OOo stack, I tried to build a version of libgcc that
ignores CANTUNWIND by commenting out the following code segment from
gcc-4.4-4.4.3/src/gcc/config/arm/unwind-arm.c.
/* Can this frame be unwound at all? */
So scratch the last two comments; ARM uses .ARM.exidx and .ARM.extable
instead of .eh_frame and friends; we should however be concerned that
.eh_frame is present -- it shouldn't be.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
More information, and another piece of the puzzle:
I began tearing apart the headers of the libgcc3_uno.so built on karmic,
and jaunty, and noticed an interesting anomaly with the program headers
between the jaunty and karmic/lucid versions of this library, the karmic
version doesn't have an
@Michael: I think there are two types of stack unwinding frames,
.eh_frame and .debug_frame; relatively recently, gcc and gas were
patched to generate only .debug_frame instead of both .eh_frame and
.debug_frame, perhaps that's triggering the problem?
--
all openoffice apps die in
See http://gcc.gnu.org/ml/gcc-patches/2009-10/msg00818.html
So what might hit us in this case is presence of .eh_frame instead of
.debug_frame, or perhaps a mix.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
A little more poking with readelf reveals that we don't actually have
any data in the .eh_frame that exists on karmic/lucid:
mcasadev...@dawn:/usr/lib/ure/lib$ readelf -x.eh_frame
./libgcc3_uno.so.karmic
Hex dump of section '.eh_frame':
0xc2c4
Turns out that readelf natively speaks .eh_frame
mcasadev...@dawn:/usr/lib/ure/lib$ readelf -Wwf ./libgcc3_uno.so.jaunty
Contents of the .eh_frame section:
0010 CIE
Version: 1
Augmentation: zR
Code alignment factor: 2
Data alignment factor: -4
Based on IRC chatter, I realized I forgot to note that the X in
XPASS/XFAIL stands for unexpected :-). Sorry about that.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug
As another round of debugging passes, I've been trying to isolate the
specific changes between karmic and jaunty which caused the regression
in the first place. I haven't been testing on lucid since it stands to
reason the cause of the UNO failure between karmic and lucid is
unchanged. The test
As requested by ARM toolchain engineers, I got a stacktrace of just
before the crash in question (when the PC is stopped just before the
__cxa_throw)
Breakpoint 5, gcc3::raiseException (pUnoExc=0xbed9652c, pUno2Cpp=0x1742c4)
at
After an intense round of debugging, toolchain bisecting, and other
crazy things, I've finally managed to pinpoint the exact location of the
crash to bridges/source/cpp_uno/gcc3_linux_arm/except.cxx:284
The code in question is the following:
if (! rtti)
{
throw
** Changed in: openoffice.org (Ubuntu)
Assignee: Matthias Klose (doko) = Michael Casadevall (mcasadevall)
** Changed in: openoffice.org (Ubuntu)
Milestone: ubuntu-9.10 = ubuntu-10.04-beta-1
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel
No, afaics the visibility bug has nothing to do with it. wether the
configure test is fixed (lucid) or not (karmic), the outcome for this
report doesn't change.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
I've been doing research on this problem, and making some notes here on
my work debugging this. I'm somewhat limited that I'm working off jocote
and dyfet's imx51 boards, but I've made some progress.
Reading an interview
(http://www.openoffice.org/editorial/peter_naulls.html) with the Peter
** Tags added: iso-testing
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: openoffice
Status: Confirmed = In Progress
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-release-notes
Status: Incomplete = Invalid
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu-release-notes
Status: New = Incomplete
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: openoffice
Status: Invalid = Confirmed
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still an issue in karmic, but we have a workaround in place (using the
jaunty binary).
** Changed in: openoffice.org (Ubuntu Karmic)
Status: Fix Committed = Won't Fix
** Changed in: openoffice.org (Ubuntu Karmic)
Importance: High = Low
** Changed in: openoffice.org (Ubuntu)
Well .jaunty works (default) but .old and .new .sos dont.
Are you referring to the PPA? I didn't find any .jaunty there, only
.old and .new, with .new being the default. Again, neither seems to
work (in -2ubuntu5~ppa1)
--
all openoffice apps die in
There's a .jaunty is the ppa version:
l...@dove-y1:~$ apt-cache policy ure
ure:
Installed: 1.5.1+OOo3.1.1-2ubuntu5~ppa1
Candidate: 1.5.1+OOo3.1.1-2ubuntu5~ppa1
Version table:
*** 1.5.1+OOo3.1.1-2ubuntu5~ppa1 0
500 http://ppa.launchpad.net karmic/main Packages
100
Ah... it looks like this package did not get upgraded when I installed
from the PPA... I will try again.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you
** Changed in: openoffice
Status: Confirmed = Invalid
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, I can now confirm lool's observation - soffice works with
libgcc3_uno.so.jaunty, but libgcc3_uno.so.{old,new} seem to suffer from
the familiar exception problem.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
1) A filesystem last mounted in future error is still treated as
serious enough to interrupt the boot process and require
interaction
via mountall-shell. My view is that this is not appopriate because
this may well happen when Windows fiddles with the clock on a
dual-boot
Argh! Please ignore that last comment from me. It relates to a
completely different bug— pasted it in the wrong tab X@
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug
supposed to be fixed, see test packages at
https://launchpad.net/~doko/+archive/toolchain
** Changed in: openoffice.org (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
Issue still persists for me with the PPA packages as well.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well .jaunty works (default) but .old and .new .sos dont.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
Binary package hint: openoffice.org
starting an openoffice app on armel only results in a splashscreen
without starting the app, starting the app from commandline gets the
following output:
o...@babbage:~$ oowriter
- javaldx: Could not find a Java Runtime
Latest attempt to work around this FTBFS on armel due to a missing
build-dependency. Pushing the milestone back to 9.10.
** Changed in: openoffice.org (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta = ubuntu-9.10
--
all openoffice apps die in
upload waiting for approval since 2009-09-26
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Great job Matthias!
Thanks,
Chris
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
this is due to bug #436617, introduced with a binutils update in
2.19.51.20090515-0ubuntu1
** Changed in: openoffice.org (Ubuntu Karmic)
Status: Confirmed = Triaged
** Changed in: openoffice.org (Ubuntu Karmic)
Assignee: Chris Cheney (ccheney) = Matthias Klose (doko)
--
all
the broken build with vfp is unrelated, fix in progress as well
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: OpenOffice.org Issue Tracker #105359
http://qa.openoffice.org/issues/show_bug.cgi?id=105359
** Also affects: openoffice via
http://qa.openoffice.org/issues/show_bug.cgi?id=105359
Importance: Unknown
Status: Unknown
--
all openoffice apps die in
** Changed in: openoffice
Status: Unknown = Confirmed
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well done Matthias! \o/
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I just heard about a possibly relevant issue. Although I don't have any
direct evidence that this is the cause, could this be related to the
interaction between exception handling and the switch to VFP? :
Codesourcery found and fixed a couple of bugs in glibc's longjmp
implementation which
here is the uno2cpp.cxx from OOo for arm; I'm unsure about the
__SOFTFP__ conditional. Shouldn't that read
#if defined(__ARM_EABI__) (!defined(__SOFTFP__) ||
defined(__ARM_NEON__) || defined(__VFP_FP__))
Isn't -mfloat-abi=softfp supposed not to change the ABI?
Note there is a similar issue
** Attachment added: uno2cpp patch
http://launchpadlibrarian.net/32302394/uno2cpp.diff
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member
@dave: the original breakage sadly predates the switch to VFP by default
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs,
Matthias, we changed the toolchain defaults after this bug had been
witnessed.
Also I change oo.o to use -mfloat-abi=soft since I thought uno2cpp.cxx
needed porting in case softfp used fpu regs to pass args in some cases
(e.g. function calls within the same binary). On second thought this
#34Oliver Grawert wrote 7 minutes ago:
@dave: the original breakage sadly predates the switch to VFP by default
Shame :( I'll flag up the toolchain patches when I have them anyway,
but I guess they may not solve this problem with OOo.
#35Loïc Minier wrote 40
I think that when functions are inlined they don't appear in the
backtraces/dont change the stack like a function, so don't need to be
handled by the exception handlers/stack parsers.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
- karmic's oo.o source built under karmic with jaunty's eglibc does not
work
that should rather be:
- karmic's oo.o source built under karmic with eglibc built with jauntys
toolchain and gcc-4.3 does not work
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException'
So Matthias did various test builds and Oliver tried various resulting binaries:
- karmic's oo.o source built under karmic and running with jaunty's
libgcc3_uno.so works
- running with libgcc3_uno.so from a jaunty oo.o build of karmic's oo.o source
works
- karmic's oo.o source built under karmic
Caolan who did the initial armel EABI port of oo.o told me to check
whether firefox and gij work fine; firefox works fine in our testing in
karmic and he proposed using
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21285 as a test case for
gij.
I built Test.java with gcj and gcj -C --main=Test and
On 22.09.2009 18:05, Loïc Minier wrote:
Caolan who did the initial armel EABI port of oo.o told me to check
whether firefox and gij work fine; firefox works fine in our testing in
karmic and he proposed using
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21285 as a test case for
gij.
I built
building the backport from chris ppa in an armel jaunty chroot still fails (
Bug #430525 ), but gets far enough to build
bridges/unxlngr.pro/lib/libgcc3_uno.so.
we tried to copy that into a karmic system which has a standard oo.o install,
firing up oo.o still fails with the same error.
this
moving on with testing, replacing the packaged karmic versions of uno-
libs3 and ure with the packages from jaunty makes the error go away,
chris is that info sufficient to find (and fix) the code changes that
made it stop working in karmic ?
--
all openoffice apps die in
copying just libgcc3_uno.so from the jaunty package into
/usr/lib/ure/lib/ on karmic makes OO.o start as well
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because
I emailed upstream to see if they have any idea what would break in that
library to cause the problem.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you
Caolan's response was the following:
The OOo source was the same in each case right ? Or was it one version
of OOo vs another ?
Do similar things to the uno bridge (i.e. libgcc3.uno.so) work in both
toolchains, e.g. libffi and mozilla have similar things. So does firefox
exist and work on the
When looking to see obvious changes between jaunty and karmic one of the
things is the version of boost used, in jaunty it is 1.35 and in karmic
it is 1.38.
Also it appears boost 1.38 got some big patches about a month ago which
might also have broken something:
11:19 ScottK ccheney: It's a
To be clear about the above comment, I am talking about what is
different about OOo 3.1.1 when built on jaunty vs karmic. We can't get
an exact duplicate build due to package versions changing, and the most
obvious of these other than the toolchain itself is the version of boost
used as noted
** Changed in: openoffice.org (Ubuntu Karmic)
Milestone: karmic-alpha-6 = ubuntu-9.10-beta
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a
trying to build the PPA packages in a jaunty armel system i end up with
the attached error
** Attachment added: OO.o-build-error.txt
http://launchpadlibrarian.net/31642974/OO.o-build-error.txt
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in
Loic,
From Oliver's build error it looks like it is possible it could be a
compiler issue. The same version of OOo on the previous arm toolchain
fails to build entirely due to toolchain problems. What is the next step
in your opinion? I can try to make OOo 3.0.1 compilable on Karmic but it
Chris, we want to workaround the toolchain issue by using smaller opts
for now and report/track/fix the toolchain issue in the mean time.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received
bug #427829 has info on teh compiler, i'll try a build with lower
optimization
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
I have a backported version of 3.1.1 in the openoffice-pkgs ppa for
jaunty that you could try out on arm I suppose. Building the OOo from
jaunty on karmic would take a lot of work since a lot of supporting
packages have changed and many are no longer available in karmic.
Note that the build on jaunty would not be 100% identical due to build
depends package version differences, but may help determine if the issue
is the toolchain.
Chris
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
they surely do since he is the expert, i have as much experience with
OO.o as you have with arm :)
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a
So Oliver points out we have a slightly different patch than the
referenced one. If the patch is only about fixing alignment issues then
it's not a big deal since I confirmed that the bug reported here doesn't
trigger any alignment traps (echo 3 /proc/cpu/alignment + watching
dmesg and cat
This might help debugging:
http://wiki.services.openoffice.org/wiki/Debugging
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
This bug might explain a gcc regression but not sure:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38732
And these are instructions for building:
http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Linux#setting_the_environment
This is his response:
Have you got workspace.cmcfixes59.patch applied ? That's got some fixes
for IA64 and ARM to ensure the desired alignment, i.e. without it an ARM
OOo built on qemu or in kernel lenient mode will auto-detect laxer
alignment that is desirable on arm. There would probably be a
This is his response:
Have you got workspace.cmcfixes59.patch applied ? That's got some fixes
for IA64 and ARM to ensure the desired alignment, i.e. without it an ARM
OOo built on qemu or in kernel lenient mode will auto-detect laxer
alignment that is desirable on arm. There would probably be a
A similar patch to the one referenced seems to already be applied.
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oli,
Does any of the stuff Caolan mentioned make sense to you? I have no
prior experience with arm at all.
Chris
--
all openoffice apps die in
'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic
https://bugs.launchpad.net/bugs/417009
You received this bug notification
1 - 100 of 110 matches
Mail list logo
