I'll be honest, I have no idea what I've done or am doing but THANK-YOU! So I followed the last few step of the thread :Ĭp vmmon.o /lib/modules/`uname -r`/kernel/drivers/misc/vmmon.koĬp vmnet.o /lib/modules/`uname -r`/kernel/drivers/misc/vmnet.ko So sticking my head in the sand (again) I moved on with the following.īefore I found this thread I tried the method in this post here which didn't work because it doesn't have a step to comment out line 65-72 as you identified in file vm_asm_x86.h (located in. Skipping BTF generation for /usr/lib/vmware/modules/source/vmnet-only/vmnet.ko due to unavailability of vmlinux So I did what I do when my car makes a bad noise I turned up the radio so I couldn't hear it and moved on.Īs far as the vmnet-only directory I'm not sure what file to modify. Make: *** No rule to make target 'install'. Now the 'Make' for vmmon went great no errors however the make install returned vmmon-only/ before doing the make and make install. Now after the install there is only the 2 tar files for vmnet and vmmon, I extracted those tar files manually (tar xvf vmnet.tar then tar xvf vmmon.tar) and modified the vm_asm_x86.h in. (likely because its vmmon and not vmnet)īecause I had been messing around trying other methods before I found this post, I decided to start over fresh again, so I reinstalled VMWare WS 16.2. I tried the steps posted here but that didn't work for me. I've installed the headers with " apt install build-essential linux-headers-$(uname uname -r VMware compile fails with " Skipping BTF generation for /tmp/modconfig-9C2Ftg/vmnet-only/vmnet.ko due to unavailability of vmlinux"īefore finding this post I've uninstalled 16.1 and tried to install 16.2 (obviously that didn't work) Whatever, just put this line in ~/.vim/after/plugin/foo.I just upgraded my Pop!_OS to 21.10 (regretting this now) and I'm receiving somewhat the same compile issue, instead of vmmon its vmnet It turns out you can do it with ~/.vim/after/ but that solution actually looks quite "hacky" to me as it mixes "plugins" and "colorschemes". You could try this plugin (never tried) but I'm not sure what you want deserves another plugin in your setup. Anyway, I'm not sure it works for your specific needs. Using the ~/.vim/after/ directory is not a hack at all: it's under-documented for sure but it's usually a lot cleaner than the equivalent mess in your ~/.vimrc. Move those lines from the plugin to your colorscheme and edit them to your liking,Īdd these lines to your ~/.vimrc: augroup M圜olorsĪutocmd ColorScheme * highlight DbgBreakptLine ctermbg=NONE ctermfg=NONE That's not very clean, unfortunately, so you basically have three workable options:Ĭhange the colors right there in the plugin, Since it is sourced after your ~/.vimrc and your colorscheme it will override any rule with the same name. vim/after.ĭid you notice that the plugin actually defines the style of that highlight group? hi default DbgBreakptLine term=reverse ctermfg=White ctermbg=Green guifg=#ffffff guibg=#00ff00 Ideally I'd like some way of customising this, without changing the plugin, or doing something hacky like putting the command inside. Sure enough, plugins are loaded after colors. I had a look at this question, and thought I would look at :scrip, which shows which files are loaded when. Given this, I had a look around the internet for any solutions to plugins overwriting config, but I couldn't find anything useful. vimrc does is load pathogen, then selects my color scheme. But how? Is it running after my color scheme? I don’t think so, because the first thing my. I can only conclude that Vdebug is clobbering my chosen styles by taking precedence somehow. However, Pasting this into a session has the desired effect. I had a look at the source, and it says I need to target a DbgBreakptLine (I don’t know what they are called, but it’s the thing you put after hi).īut if I put: hi DbgBreakptLine ctermbg=NONE ctermfg=NONE I’m trying to set up some prettier highlighting for Vdebug.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |