xsilentmurmurx Posted January 13, 2018 Report Share Posted January 13, 2018 hello everyone I am trying to emerge KDE Plasma 5 and everything is emerging fine, but when I get to xfce-base/libxfce4util-4.13.1, the emerging fails. I tried to emerge it separately and it still fails. here is the build.log for xfce-base/libxfce4util-4.13.1: https://paste.pound-python.org/show/ozz1CuzVsUsOwFi25PKE/ Please let me know if there is anything info I need to provide Thanks! Link to comment Share on other sites More sharing options...
0 Oleg Vinichenko Posted January 14, 2018 Report Share Posted January 14, 2018 su - or su -l is recommended as in this case you're getting clean environment not contaminated with any variables such as XDG_CACHE_HOME and which was the origin of a failure. Link to comment Share on other sites More sharing options...
1 palica Posted January 13, 2018 Report Share Posted January 13, 2018 try su - should set also environment variables Link to comment Share on other sites More sharing options...
0 xsilentmurmurx Posted January 13, 2018 Author Report Share Posted January 13, 2018 38 minutes ago, jhan said: It seems your emerge fails while trying to create the directory /home/majid/.cache/g-ir-scanner. Not sure why. I just installed it on my system without problem. The only thing that seems to be different is the USE flag introspection. It seems to me that you installed it with "+introspection" while my installation was with ""-introspection". If you don't really need the "support for GObject based introspection" for this package I would suggest trying to install it with "-introspection" and see how it goes. Thank you for the reply Emerging it with USE="-introspection" worked, but the problem is when I run this command to update the system and emerge KDE Plasma 5: emerge -auvDN --with-bdeps=y @world kde-plasma/plasma-meta it forces libxfce4util to emerge with USE="+introspection" . Any idea on how I can fix this? Thanks! Link to comment Share on other sites More sharing options...
0 Oleg Vinichenko Posted January 13, 2018 Report Share Posted January 13, 2018 this failure could happen if your XDG environment incorrectly set. Thats when you start compilation in GUI (terminal emulator), some XDG* variables have special values. TO check, run following in terminal you used: declare -p ${!XDG*} Link to comment Share on other sites More sharing options...
0 xsilentmurmurx Posted January 13, 2018 Author Report Share Posted January 13, 2018 2 hours ago, Oleg Vinichenko said: this failure could happen if your XDG environment incorrectly set. Thats when you start compilation in GUI (terminal emulator), some XDG* variables have special values. TO check, run following in terminal you used: declare -p ${!XDG*} thank you for the response Oleg Here you go: # declare -p ${!XDG*} declare -x XDG_CACHE_HOME="/home/majid/.cache" declare -x XDG_CONFIG_DIRS="/etc/xdg" declare -x XDG_CONFIG_HOME="/home/majid/.config" declare -x XDG_CURRENT_DESKTOP="LXQt" declare -x XDG_DATA_DIRS="/usr/local/share:/usr/share" declare -x XDG_DATA_HOME="/home/majid/.local/share" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/majid" declare -x XDG_MENU_PREFIX="lxqt-" declare -x XDG_SEAT="seat0" declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" declare -x XDG_SESSION_COOKIE="funtoohost-1515048768.293209-672040983" declare -x XDG_SESSION_DESKTOP="lxqt" declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session1" declare -x XDG_SESSION_TYPE="x11" declare -x XDG_VTNR="7" Link to comment Share on other sites More sharing options...
0 Oleg Vinichenko Posted January 13, 2018 Report Share Posted January 13, 2018 so, that's the problem. normally XDG_CACHE_HOME=/root expected. How do you use your terminal root? Via su, sudo, etc? Link to comment Share on other sites More sharing options...
0 xsilentmurmurx Posted January 13, 2018 Author Report Share Posted January 13, 2018 8 hours ago, Oleg Vinichenko said: so, that's the problem. normally XDG_CACHE_HOME=/root expected. How do you use your terminal root? Via su, sudo, etc? Ahh I see.. I usually su into the root account Link to comment Share on other sites More sharing options...
0 xsilentmurmurx Posted January 13, 2018 Author Report Share Posted January 13, 2018 8 minutes ago, palica said: try su - should set also environment variables You never fail me Palica :) That worked!! Thank you! I am now emerging KDE Plasma 5. .Hopefully I wont run into any more issues. Do you recommend that when I emerge packages, I use su - first to switch into the root user and load all of the root user's environment variables? Link to comment Share on other sites More sharing options...
Question
xsilentmurmurx
hello everyone
I am trying to emerge KDE Plasma 5 and everything is emerging fine, but when I get to xfce-base/libxfce4util-4.13.1, the emerging fails. I tried to emerge it separately and it still fails.
here is the build.log for xfce-base/libxfce4util-4.13.1:
https://paste.pound-python.org/show/ozz1CuzVsUsOwFi25PKE/
Please let me know if there is anything info I need to provide
Thanks!
Link to comment
Share on other sites
8 answers to this question
Recommended Posts