| Summary: | OpenOffice.org ebuild: CHECKREQS_DISK_BUILD should be raised | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Nagel <juergennagel> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Juergen Nagel
2006-08-24 18:59:44 UTC
Please, note that on the pending bug about HW requirements. Thanks. *** This bug has been marked as a duplicate of 140867 *** I dare to differ, that's another problem. Though one I can't reproduce at all, 5120 MB is more than sufficient here unless you use the debug use flag (did you?) Also please always provide your "emerge info" I just had a second look on the ebuild and saw the fail condition differentiating between having specified the debug flag or not. Then it came to me that I had added "-ggdb" to my CFLAGS to debug some KDE crashes. Would it be possible to enhance the fail condition by some checks for CFLAGS causing the build to require more space? (In reply to comment #3) > I just had a second look on the ebuild and saw the fail condition > differentiating between having specified the debug flag or not. > Then it came to me that I had added "-ggdb" to my CFLAGS to debug some KDE > crashes. > > Would it be possible to enhance the fail condition by some checks for CFLAGS > causing the build to require more space? > Might be possible, but actually if you use non-default-use-flags you really should know what you are doing ;) Also the warning is only a guideline (it doesn't fail per default), so closing |