| Summary: | sys-apps/which and other packages stop emerge builds - When `ar ...` gets executed - ERROR: no command given - Usage: start_ar.rb <command> <options> -- <application options> | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin <Martin.Baus> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | base-system, Martin.Baus |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
build.log environment |
||
|
Description
Martin
2013-02-27 22:38:21 UTC
Created attachment 340426 [details]
emerge --info
Created attachment 340428 [details]
build.log
Created attachment 340430 [details]
environment
Attached the files for you. Whereas we didn't get this resolved on chat, the mantainers of which and binutils (which contains ar) probably have more expertise on this; we already checked up the symlink which resolves the PATH correctly, so we had no clue where it gets start_ar.rb from. Hopefully one of the maintainers knows what is going on and perhaps we can then turn this bug into something that will prevent this kind of behavior in the future. google says `start_ar.rb` is a random ruby file from something called "auto_response" |