Virtualbox 5&6 - MX/antiX kernel conflicts [SOLVED]

[manyroads]

Yes, is this the Liquorix kernel from our test repo, via the package installer?

Yes!

[manyroads]

That eliminates one possible issue. How about running:

Code: Select all

/usr/src/linux-headers-5.0.0-14.1-liquorix-amd64/scripts/gcc-version.sh -p gcc

Tim I get the following:

Code: Select all

$ /usr/src/linux-headers-5.0.0-14.1-liquorix-amd64/scripts/gcc-version.sh -p gcc
060300

[timkb4cq]

That kind of puts me at a loss because your build log has

Code: Select all

./scripts/gcc-version.sh: line 26: gcc: command not found
./scripts/gcc-version.sh: line 27: gcc: command not found

but the script runs fine from the command line.

Only one thing occurs to me now, and it's a long shot, but lets see

Code: Select all

echo $PATH
sudo echo $PATH

[manyroads]

That kind of puts me at a loss because your build log has

Code: Select all

./scripts/gcc-version.sh: line 26: gcc: command not found
./scripts/gcc-version.sh: line 27: gcc: command not found

but the script runs fine from the command line.

Only one thing occurs to me now, and it's a long shot, but lets see

Code: Select all

echo $PATH
sudo echo $PATH

Thanks again, Tim.

Here are the results...

Code: Select all

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin
mark@mark-dell:~
$ sudo echo $PATH
[sudo] password for mark: 
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin
mark@mark-dell:~

[timkb4cq]

Yup, still at a loss. Unless you installed other gcc versions and messed with the symlinks I can't think how that script works from the terminal but not when dkms calls it.
That same version gcc & virtualbox works properly here.

[manyroads]

Yup, still at a loss. Unless you installed other gcc versions and messed with the symlinks I can't think how that script works from the terminal but not when dkms calls it.
That same version gcc & virtualbox works properly here.

I can say for certain I did not mess with the symlinks (myself, manually). The only symlinks I create are for thunderbid and couple of small apps to get access to my Dropbox folders. Having said that , I almost certainly have a 'collection' of gcc installs.

Here's my listing:

Code: Select all

ii  clang                                           1:3.8-36                          amd64        C, C++ and Objective-C compiler (LLVM based)
ii  clang-3.8                                       1:3.8.1-24                        amd64        C, C++ and Objective-C compiler (LLVM based)
ii  g++                                             4:6.3.0-4                         amd64        GNU C++ compiler
ii  g++-6                                           6.3.0-18+deb9u1                   amd64        GNU C++ compiler
ii  gcc                                             4:6.3.0-4                         amd64        GNU C compiler
ii  gcc-6                                           6.3.0-18+deb9u1                   amd64        GNU C compiler
ii  libllvm3.8:amd64                                1:3.8.1-24                        amd64        Modular compiler and toolchain technologies, runtime library
ii  libllvm7:amd64                                  1:7-6~mx17+1                      amd64        Modular compiler and toolchain technologies, runtime library
ii  libxkbcommon0:amd64                             0.7.1-2~deb9u1                    amd64        library interface to the XKB compiler - shared library
ii  linux-compiler-gcc-6-x86                        4.20-2~mx17+1                     amd64        Compiler for Linux on x86 (meta-package)

Perhaps one of these broke something.

[manyroads]

Another update (good news).

After running the following:

Code: Select all

sudo apt install --reinstall gcc

I used MXPI to install several of the previous kernels that failed dkms earlier.

They all work without error now. The reinstall seems to have 'fixed' whatever was broken.

I'll mark the problem [solved].