| Summary: | segfaults in open-office-bin-2.4.1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Benjamin Schulz <schulz.benjamin> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED INVALID | ||
| Severity: | critical | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Benjamin Schulz
2008-06-30 15:24:41 UTC
I re-emerged openssl and glibc with O2 Cflags and the problem dissapeared. I don't know why but it doesn't occur anymore. I think the ebuild of openoffice-bin should contain a warning that users might have to reemerge openssh and glibc, because in the forums, it seems that many others have this problem. Reemerging openssh shouldn't matter in this case. Reemerging openssl might, but it's unclear how. You should probably attach a backtrace log of /usr/bin/soffice to this bug. you are correct, of course. It was simply a typo I made here. Of course I re-emerged openssl and glibc. Sorry but I cannot add a backtrace log, because i cleaned them after it worked. I only think that one should add a message to the ebuild of re-emerging glibc and openssl with O2. -02 is default, if you raise your CFLAGS you are on your own, no way are we going to warn about each and every CFLAGS combination in all ebuilds. Nothing we can do here... |