srb2bld -ra and -rb before I would retry installing Kart Moe! Still, another issue arises:
It seems you did well. First of all, could you show me output of command
find /usr/local/lib -iname libdiscord-rpc.so? If path to file libdiscord-rpc.so shows for you, then try to run export LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH" and run again srb2kartmoe. If that works, add that LD_LIBRARY_PATH command to your shell configuration file like .bash_profile or .bashrc or .zshrc.
Er, nevermind it all. Dunno what woinkings and jinxings has my PC been up to, but the error has disappeared away and now lets me start my game with Discord RPC, just after I restarted on my computer. Oh.
Fantastic update! Building up custom SRB2 builds is sure a fancy feature! Speaking off, that's something I'm trying to use at the moment, yet I'm falling miserably sadly... for some forsaken reason, srb2bld just spats out that my SBR2GITPATH isn't set, despite that I did so on my .bash_profile.
It's a particular SRB2Kart custom build I'm trying to compile yet. I'd suppose that's not supported yet? It's hosted on Gitlab too! If either are truly supported, then no idea what's causing the discrenpancy here.
source ~/.bash_profile, and then run script? If yes and your issue still persists, then could you show me output of echo $SRB2GITPATH from newly opened terminal, so we can figure out what's going on?export SRB2GITPATH="[your-path-to-your-custom-repository]" was not written to ".bash_profile" in user's home directory,echo $0,
Oh, yes! Though, erm, just as I was about to follow through your steps, I got hit with this another exorbitant issue, and it won't let me compile any of SRB2 builds at all, even with your up to date script. Really odd...
This issue is fixed with new update. I would like to apologize, I messed up with variables within script from previous update, that resulted with wrong versions of GCC.
Oh, don't be sorry! I'm just very grateful enough to be reporting issues and being on my good part to round up better your useful script! Thanks a ton for your efforts, as always!
This is security measure with recently updated Git, that conflicts with Docker container. I updated script, to fix this issue.Oh, don't be sorry! I'm just very grateful enough to be reporting issues and being on my good part to round up better your useful script! Thanks a ton for your efforts, as always!
In any case, now I'm getting this "git" issue as of lately:
And though I did "sudo" input that recommending exact commands afterwards, I still get the same error.
Thank you, that did plumb on the problem! Although, I think you might have forgotten to fix this for DiscordRPC's libs too.
Oof, you are right. I just updated script again in my GitHub repository, this time it affects libraries downloaded from Git repositories too.Thank you, that did plumb on the problem! Although, I think you might have forgotten to fix this for DiscordRPC's libs too.