Summary: | * WARNING: The FEATURES variable contains one or more values that should be disabled under normal circumstances: keepwork | ||
---|---|---|---|
Product: | Portage Development | Reporter: | renesanso <renesanso> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/etc/make.conf
emerge xen-tools errors log copypaste |
Description
renesanso
2012-09-09 15:19:19 UTC
Created attachment 323316 [details]
/etc/make.conf
Created attachment 323318 [details]
emerge xen-tools errors log copypaste
* WARNING: The FEATURES variable contains one or more values that * should be disabled under normal circumstances: keepwork (In reply to comment #3) > * WARNING: The FEATURES variable contains one or more values that > * should be disabled under normal circumstances: keepwork And what? This option must prevent stopping when some errors occurred. (In reply to comment #0) > When I do "rm -rf /var/tmp/portage/app-emulation/xen-tools-4.1.2-r3" (and > "rm -rf /var/tmp/portage/*" for solve problem global) all compiles ok, but > when I recompile apps, I have not any benefit, because this cache was > deleted. Mostly packages compiles without cleaning cache. With FEATURES=keepwork, it doesn't recompile anything. It only runs the src_install phase again with the previously compiled files. If you really want a cache, then ccache is is more appropriate. I wouldn't recommend it though, because it's error-prone. (In reply to comment #5) > (In reply to comment #0) > > When I do "rm -rf /var/tmp/portage/app-emulation/xen-tools-4.1.2-r3" (and > > "rm -rf /var/tmp/portage/*" for solve problem global) all compiles ok, but > > when I recompile apps, I have not any benefit, because this cache was > > deleted. Mostly packages compiles without cleaning cache. > > With FEATURES=keepwork, it doesn't recompile anything. It only runs the > src_install phase again with the previously compiled files. > > If you really want a cache, then ccache is is more appropriate. I wouldn't > recommend it though, because it's error-prone. Oh, thanks. I really don't understand right what this option do. In what cases ccache may be error-prone (example: if update some application, or eaven for recompile the same)? Maybe there is some solutions to make using ccache safe? And (most interesting) it may be only errors during compilation with ccache, or I can have segfault or other errors in runtime, but all will compile normaly? (In reply to comment #6) > Oh, thanks. I really don't understand right what this option do. keepwork? If the corresponding documentation in `man make.conf` isn't enough for you, then you shouldn't be using it. I'd like to remove the feature because it's easy for people to hurt themselves with it, but I don't because it may still be useful for people who understand it. > In what > cases ccache may be error-prone (example: if update some application, or > eaven for recompile the same)? Maybe there is some solutions to make using > ccache safe? > > And (most interesting) it may be only errors during compilation with ccache, > or I can have segfault or other errors in runtime, but all will compile > normaly? I don't use ccache, so I'm not really familiar with all of its failure modes. It's a third-party application, so you should check the documentation that comes with it. |