I also get GLOBAL_OFFSET_TABLE error -2. I get errors like this, seemingly for every kernel module: ".../kernel/crypto/cmac.ko.xz is not a valid ELF object" I tried both the github master link below and the AUR package. I did not understand which was the latest or most suitable. I did not understand the comment before this one, if there was something I should change in the installation. What I use is 32 bit linux. archlinux32. I use the pentium4 architecture but compile the components with march=i686. The kernel is 5.3.1-arch1-1.0.ARCH. It's an Intel Pentium 4 computer.
Search Criteria
Package Base Details: oss-git
Git Clone URL: | https://aur.archlinux.org/oss-git.git (read-only, click to copy) |
---|---|
Keywords: | oss |
Submitter: | Nowaker |
Maintainer: | Galaxy |
Last Packager: | Galaxy |
Votes: | 25 |
Popularity: | 0.047982 |
First Submitted: | 2013-09-21 13:15 |
Last Updated: | 2019-11-01 17:19 |
Packages (2)
erlhel commented on 2019-10-14 00:40
seawright commented on 2019-10-10 19:48
Pull request sent.
Note: Should be patch -p3 <...
in PKGBUILD to apply patch as left a/ and b/ in diff file.
Galaxy commented on 2019-10-10 02:41
@seawright
You can send pull request to <https://github.com/GalaxyAUR/oss-git/tree/master>.
seawright commented on 2019-10-09 21:28
It would appear that a 2nd kmod-link patch is required to fix the other Makefile in the /usr/lib/oss/build directory.
The install script install.sh also requires patching but it's too long to include in a comment. Would it be OK to email it to the package maintainer?diff -ru setup/Linux/oss/build.orig/Makefile.tmpl setup/Linux/oss/build/Makefile.tmpl --- setup/Linux/oss/build.orig/Makefile.tmpl 2019-10-09 12:48:41.351431860 +0100 +++ setup/Linux/oss/build/Makefile.tmpl 2019-10-09 20:46:45.143954962 +0100 @@ -5,6 +5,7 @@ ifneq ($(KERNELRELEASE),)
obj-m := MODNAME.o + MODNAME-objs := MODNAME_wrapper.o MODNAME_mainline.o
else
seawright commented on 2019-10-09 21:15
After upgrading Linux kernel from 5.1.21 to 5.2.3 with the exception of osscore.ko kernel modules failed to compile. Build list gave following error report:
Building modules, stage 2.
MODPOST 1 modules
ERROR: "lynxone_attach" [/usr/lib/oss/build/lynxone.ko] undefined!
ERROR: "lynxone_detach" [/usr/lib/oss/build/lynxone.ko] undefined!
scripts/Makefile.modpost:91: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 1
Makefile:1604: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.2.3-050203-generic'
Makefile:15: recipe for target 'default' failed
make: *** [default] Error 2
Midna commented on 2019-08-27 01:37
The package compiles fine, but the osscore module still throws a GLOBAL_OFFSET_TABLE error, except it is now error -2 instead of 0.
Using GCC 9.0.1. Any fix?
Galaxy commented on 2019-07-24 11:47
I merge the version on <https://github.com/GalaxyAUR/oss-git>.
Added "-fno-pic -fno-PIE" for GCC > 5.
And change to "-O2" from "-O3".
Xylemon commented on 2019-07-24 03:15
@Galaxy,
export CC=gcc-5
export CXX=g++-5
export CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong"
export CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong"
That's all I added to the PKGBUILD, which worked for a while, although it seems I'm having trouble again with latest kernel. I've just given up again to be honest.
Galaxy commented on 2019-07-23 12:33
@Xylemon, Would you share your patch that make oss-git compile ?
Xylemon commented on 2019-07-22 20:48
I sadly can not get this to load unless I mod the script to compile with GCC5 (this is also with the GalaxyAUR Git repo). With latest GCC(9), osscore fails to load with this message:
[37591.137560] usbcore: deregistering interface driver oss_usb
[37613.232300] osscore: Unknown symbol GLOBAL_OFFSET_TABLE (err -2)
Unfortunately, another issue pops up when using OpenAL, see here: https://forum.artixlinux.org/index.php/topic,1064.0.html
I hope these issues can be resolved.
Pinned Comments
Galaxy commented on 2019-10-24 02:55
The latest support Intel HDA is
0x8c20
, and I am usinga348
. If your sound card is not listed there, it is not supported.