Summary: | dev-qt/qtwebengine-5.15.0 - /bin/sh: rcsT: inaccessible or not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | dm9pZCAq <v> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jstein, kfm |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
emerge --info |
Description
dm9pZCAq
2020-08-25 12:29:57 UTC
Thank you for the report. We need to have all information at hand before ticket assignment. That is why I ask you to * attach the logs and * paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket Please reopen this ticket (Status:UNCONFIRMED) afterwards. Created attachment 656638 [details]
build log
Created attachment 656640 [details]
emerge --info
Have you tried building with 'ccache' disabled? yes same error (In reply to dm9pZCAq from comment #3) > Created attachment 656640 [details] > emerge --info This reveals lksh as being the active /bin/sh implementation. Note that lksh is a command interpreter intended exclusively for running legacy shell scripts. Gentoo installs /bin/lksh in the case that app-shells/mksh is built with USE="lksh". Under NO circumstances should it be selected as the sh(1) provider. If you want to use the MirBSD Korn Shell for this purpose, then have the symlink point to mksh, not lksh. (In reply to Kerin Millar from comment #6) > (In reply to dm9pZCAq from comment #3) > > Created attachment 656640 [details] > > emerge --info > > This reveals lksh as being the active /bin/sh implementation. Note that lksh > is a command interpreter intended exclusively for running legacy shell > scripts. Gentoo installs /bin/lksh in the case that app-shells/mksh is built > with USE="lksh". Under NO circumstances should it be selected as the sh(1) > provider. If you want to use the MirBSD Korn Shell for this purpose, then > have the symlink point to mksh, not lksh. ok, thank you for help and sorry for that |