Summary: | QA: openoffice-2.0.3 contains executable stacks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Bettler <thomas.bettler> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | rockoo, wsartori |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /var/tmp/portage/openoffice-2.0.3/temp/scanelf-execstack.log |
Description
Thomas Bettler
2006-07-05 07:15:33 UTC
Created attachment 90967 [details]
/var/tmp/portage/openoffice-2.0.3/temp/scanelf-execstack.log
any info about this bug? I compile the openoffice in 20 hours and now I can't install it because of this bug. Using openoffice-bin is not an option. thanks (In reply to comment #2) > any info about this bug? I compile the openoffice in 20 hours and now I can't > install it because of this bug. Using openoffice-bin is not an option. thanks > That bug is non-harmful, so it shouldn't prevent you from installing, if it drops out, that would be another thing (but that's not what this bug is about...) oops, accidental reassign, fixing I give 100% of processing installing this file! After this it stops to install using ebuild openoffice.ebuild install (In reply to comment #5) > I give 100% of processing installing this file! After this it stops to install > using ebuild openoffice.ebuild install > the cpu power is not used for installing this file but for various checks for OOo and as OOo is quite big this needs some time, so normally you'll just have to wait. btw: any reason you use ebuild openoffice.ebuild install instead of a normal emerge? (also without qmerge afterwards this won't get you OOo to the filesystem...) We now work around this (until it is solved upstream), so closing this |