Summary: | emerge corrupts package build log in case of build errors | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eugene Shalygin <eugene.shalygin> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | ajak, ionen, jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | sample build log with errors |
Description
Eugene Shalygin
2021-03-23 17:31:00 UTC
Created attachment 693267 [details]
sample build log with errors
What do you mean corrupted? Are you referring to ansi colors? You can strip those using something like app-text/ansifilter I don't know, maybe ANSI color sequences are to blame. My less can't show content around error in the log file left after emerge, but is able to do that with the file from ebuild (also with color sequences). less -R less -R shows the same crappy output, less -r is less corrupted, but still impossible to read errors. (In reply to Eugene Shalygin from comment #5) > less -R shows the same crappy output, less -r is less corrupted, but still > impossible to read errors. Looks funky through a pager for me, but `cat`ing it straight into a terminal looks fine. It seems the characters the package outputs at build time make the log look funny to us in pagers, but this is certainly not an emerge issue. |