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 configuration. I agree we should go with -marm for now and focus on fixing the problem in time for lucid-rc. For tracking problems of this type, especially when the debugger itself has some issues, it would be valuable to reconfigure the buildds to save core dumps for process crashes occurring during builds. Do you know who we can discuss that with? In the meantime, can you fire off a manual build, or is this one of these problems that only happens on the buildds? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
