partially related to bug #220026 (and its duplicate bug #234495). As in subject can be useful IMHO to add a use flag in order to disable the filtering of cflags for testing purpose or to solve singular (only in the buggy hardware of mine I think) hardware problems than I have also reported. Because OOo is one of the most painful packages to compile have the choiche to stop the build and restart it can be also useful. Something as: [-f "$(S)/configure-done"] || { cd "$(S)" ./configure ... touch ./configure-done} in src_compile funcion by example. Reproducible: Always Steps to Reproduce:
About the first point: I've answered that before (if you search): I see no gain in making it easier to break the build and me than having to deal with bogus bug-reports. About continuing the build: Would be nice indeed, if you want that provide a working patch (= no priority for me atm)
(In reply to comment #1) > About the first point: I've answered that before (if you search): I see no gain > in making it easier to break the build and me than having to deal with bogus > bug-reports. USE=custom-cflags is marked as 'not supported' in other packages, so it's unreasonable to speak about its danger. On the other hand, OOo runs a bit faster when compiled with -O2 (I have successfully done it on default/linux/amd64/2008.0 with gcc-4.3.2).
Created attachment 175273 [details] ebuild used for OOo 3.0
openoffice is on the way out, so see bug #355981 for libreoffice instead
