Summary: | portupgrade of editors/openoffice .org-1.0.3 stalls running installer | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | areilly | ||||
Component: | Individual Port(s) | Assignee: | freebsd-openoffice (Nobody) <openoffice> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | ||||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
areilly
2003-05-11 10:00:35 UTC
Responsible Changed From-To: freebsd-ports-bugs->openoffice Over to maintainers State Changed From-To: open->analyzed The problem is that our openoffice install assumes that no previous version is installed at the same location. If thats the case, it will just hang. So please move the old openoffice dir to a backup location, then try again and report your success. Hi, I've just tried installing openoffice again, and it stalled again (several times), and it has finally failed in the same way that I described before. I made certain that all traces of openoffice had been removed from my system before starting the build process. The screen image that I attached to my previous report was what happened when I tried to start openoffice after the installation process finished. However, the installation process did not get to "finished" without intervention from me: In several places during the build, saxparser stalled, and I killed that process and restarted the make (without first cleaning everything up) and it continued. saxparser had been busy building what looked like i18n modules for languages/locales that I don't care about, so I was not concerned if they were corrupted. At the end, when the make install process (i.e., top-level BSD port make) said: ===> Installing for openoffice-1.0.3_2 Initializing installation program.......... *** Error code 255 (ignored) ===> Generating temporary packing list ===> Add wrapper scripts ===> Registering installation for openoffice-1.0.3_2 ===> SECURITY REPORT: That Error code 255 (ignored) was me killing the soffice.bin executable, because it had been consuming 90+% of the CPU for the whole night, and that seemed unreasonable. These problems (and the others that I'm experiencing with sawfish) seem to me to be consistent with deadlock conditions in multi-threaded applications that are making unwarrented assumptions about the thread implementation, or perhaps bugs in the thread implementation. I'm thinking of upgrading to 5.x, just to get kernel-based threads, to be more like Linux and Solaris, where these applications are presumably more tested. Is that a reasonable approach? -- Andrew State Changed From-To: feedback->closed If this is still a problem with the latest (3.23.58) one, please resubmit the problem. Most likely it was caused by the not running of ldconfig by the port. If it still occures, please add the output of "ldconfig -r" to the PR. State Changed From-To: open->open euhmm.. I'll redit this PR. State Changed From-To: open->open State Changed From-To: open->open State Changed From-To: open->open Fix synopses. State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix category State Changed From-To: open->open Fix synopsesFix synopsesFix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: open->open Fix synopses State Changed From-To: analyzed->analyzed Fix synopses State Changed From-To: analyzed->closed ports/61760 describes the same issue, no need to keep both PRs. |