Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 738926 - dev-qt/qtwebengine-5.15.0 - /bin/sh: rcsT: inaccessible or not found
Summary: dev-qt/qtwebengine-5.15.0 - /bin/sh: rcsT: inaccessible or not found
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Qt Bug Alias
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-25 12:29 UTC by dm9pZCAq
Modified: 2021-01-12 13:43 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build log (dev-qt:qtwebengine-5.15.0:20200825-111916.log,31.87 KB, text/plain)
2020-08-25 16:23 UTC, dm9pZCAq
Details
emerge --info (emerege.info,18.09 KB, text/plain)
2020-08-25 16:23 UTC, dm9pZCAq
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dm9pZCAq 2020-08-25 12:29:57 UTC
i'm trying to compile dev-qt/qtwebengine but i get an error (same error with 5.14.2 and 5.15.0): `/bin/sh: rcsT: inaccessible or not found`
while compiling with both gcc9.3 and gcc10.2, but with clang10 there is no such error

build log: https://0x0.st/igGm.log
emerge --info: https://0x0.st/igGy.info

Reproducible: Always
Comment 1 Jonas Stein gentoo-dev 2020-08-25 15:12:07 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.
Comment 2 dm9pZCAq 2020-08-25 16:23:04 UTC
Created attachment 656638 [details]
build log
Comment 3 dm9pZCAq 2020-08-25 16:23:38 UTC
Created attachment 656640 [details]
emerge --info
Comment 4 Chiitoo gentoo-dev 2020-08-27 18:37:51 UTC
Have you tried building with 'ccache' disabled?
Comment 5 dm9pZCAq 2020-08-29 11:18:06 UTC
yes

same error
Comment 6 kfm 2021-01-07 14:41:46 UTC
(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.
Comment 7 dm9pZCAq 2021-01-12 13:23:48 UTC
(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