You are not logged in.
sudo modprobe vboxsf
modprobe: ERROR: could not insert 'vboxsf': Exec format error
sudo journalctl -b
...
июл 05 09:21:42 arch32 kernel: vboxsf: version magic '5.0.7-arch1-1.0-ARCH SMP preempt mod_unload 686 ' should be '5.1.15-arch1-1.0-ARCH SMP preempt mod_unload 686 '
Offline
Could be related to:
https://buildmaster.archlinux32.org/bui … ild-log.gz
/startdir/PKGBUILD: line 26: cd: /var/lib/dkms/vboxhost/6.0.8_OSE/5.1.15-arch1-1.0-ARCH/pentium4/module: No such file or directory
are you on the i686 or on the pentium4 branch?
Offline
I did not specify - for the guest system: (pacman -S virtualbox-guest-modules-arch ... OK)
branch: 'pentium4'
Last edited by Lithium (2019-07-07 06:50:11)
Offline
ok. I rescheduled all virtualbox stuff, let's see if everything rebuilds..
Offline
virtualbox also has a rebuild problem around an ancient libstdc++5.
Offline
That's curious. A problem building against an old libstdc++; that's the C++ standard library and only really written in plain old C++90, so the build system for that should be pretty vanilla and have far less of the complexity of a rust build or something javaish. Presumably it's just that it links against and uses headers from a version that's older than they one you've got?
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
http://lists.busybox.net/pipermail/buil … 02526.html
seems gcc 3 and old libstdc++ need a backport.
Offline
Ah, more portability fun:
/build/virtualbox/src/VirtualBox-6.0.8/include/VBox/VBoxGL2D.h:116:19: error: conflicting declaration ‘ty
pedef ptrdiff_t GLsizeiptr’
116 | typedef ptrdiff_t GLsizeiptr;
| ^~~~~~~~~~
Offline
@levi: well, there where non-standard things in older gcc versions, and the compiler got more standard.
So usually you can compile a gcc 3 with a gcc 4, a gcc 4 with a gcc 5, but trying to build a gcc 3 with a gcc 9
is a little bit too much, I think.
Anyways: virtualbox should be ashamed they are still using such an ancient libstdc++, can't be that hard
to rewrite it in a little bit more modern C++.
Offline
Virtualbox is currently also obviously not even compiled by the developers on 32-bit before releasing, so..
Offline
Oh right, if it depends on the version of libstdc++ used by virtualbox then virtualbox clearly doesn't work the way I thought it did. I guess that's part of the reason it's so much quicker than Qemu is, and I've only had a quick play with that. I don't think the hardware I currently run had the right cpu flags to run virualbox FWIW.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Maybe when building guest-modules-arch, the kernel version should be specified - 5.1.15, which is the same as the linux kernel instead of 5.0.7? I used to save the old linux kernels required by vboxsf - it worked.
Offline
Old kernels: https://archive.archlinux32.org/packages/l/linux/
To force install a module with the wrong signature:
sudo modprobe -f vboxsf(Attention! copying files from a folder (ntfs) to btrfs using pcmanfm - corrupts files, backwards - ok. Through the terminal - OK in both directions.)
Last edited by Lithium (2019-08-15 14:25:40)
Offline