On Wed, Apr 24, 2019 at 02:33:32PM +0200, Milian Wolff wrote: > Hey all, > > for some reason, my `kdesrc-build` uses a different environment than my > normal > shells. I have so far not figured out why that is: > > $ env | grep "^PATH=" > PATH=/home/milian/.bin:/home/milian/projects/compiled/other/bin:/home/ > milian/.bin/kf5:/home/milian/projects/compiled/kf5-dbg/bin:/home/milian/ > projects/compiled/other/bin:/home/milian/projects/compiled/kf5/bin:/usr/local/ > sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/ > bin/vendor_perl:/usr/bin/core_perl > > $ kdesrc-build --run env | grep "^PATH=" > PATH=/bin:/home/milian/.bin:/home/milian/projects/compiled/other/bin:/home/ > milian/.bin/kf5:/home/milian/projects/compiled/kf5-dbg/bin:/home/milian/ > projects/compiled/other/bin:/home/milian/projects/compiled/kf5/bin:/usr/local/ > sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/ > bin/vendor_perl:/usr/bin/core_perl > > Note how it prepends /bin to PATH, which leads to all kinds of nasty side > effects for me. I want my PATH to be used as-is, most notably such that some > of the tools I've built myself get picked up, rather than the versions I have > available globally in /bin. > > Does anyone know where this could come from?
I suspect it's a kdesrc-build bug and that you have one or both of the `kdedir`, `qtdir` kdesrc-build options unset. This is fine (`kdedir` will fallback to `prefix`, `qtdir` is not required since you can use system Qt), but probably results in something like "/bin:" getting prepended to your path instead of "/path/to/custom/qt/bin:". Please see https://invent.kde.org/kde/kdesrc-build/issues/29 for the bug report. I have built a patch that might work and would appreciate if you could test. Regards, - Michael Pyne
