SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
development/gcc5—Patch to fix the build under Slackware-current.
Fix build with glibc 2.28, which lacks header file <sys/ustat.h>;
Cosmetic issues:
Fix the TAG value, to ensure it starts with an underscore (‘_’);
Insert a missing hash sign (‘#’) on a comment line, to keep the system from attempting to run a nonexistent ‘only’ command.
Code:
diff --git a/development/gcc5/gcc5.SlackBuild b/development/gcc5/gcc5.SlackBuild
index 7054b3184f..f9a03116c5 100644
--- a/development/gcc5/gcc5.SlackBuild
+++ b/development/gcc5/gcc5.SlackBuild
@@ -57,7 +57,7 @@ PRGNAM=gcc5
VERSION=${VERSION:-5.5.0}
MAJVER=$(echo ${VERSION} |cut -d. -f1)
BUILD=${BUILD:-1}
-TAG=${TAG:-SBo}
+TAG=${TAG:-_SBo}
# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
@@ -195,6 +195,9 @@ ANTLJAR=$(echo $CWD/antlr-*.jar | tail -1)
cat $CWD/patches/0009-x86-Disallow-mindirect-branch-mfunction-return-with-.diff | patch -p2 --verbose || exit 1
cat $CWD/patches/0009-x86-Disallow-mindirect-branch-mfunction-return-with-doc.diff | patch -p2 --verbose || exit 1
+ # Fix build with glibc 2.28, which no longer makes available header file <sys/ustat.h>
+ cat $CWD/patches/glibc2.28-ustat.diff | patch -p0 --verbose || exit 1
+
# Fix perms/owners
chown -R root:root .
find . -perm 777 -exec chmod 755 {} \;
@@ -434,7 +437,7 @@ fi
if [ ${MULTILIB} = "NO" ]; then
# Make our 64bit gcc look for 32bit gcc binaries in ./32 subdirectory:
- (only needed if gcc was compiled with disable-multilib)
+ # (only needed if gcc was compiled with disable-multilib)
if [ "$ARCH" = "x86_64" ]; then
sed -i 's#;.\(:../lib !m64 m32;\)$#;32\1#' \
$PKG/usr/lib${LIBDIRSUFFIX}/gcc/${TARGET}/${VERSION}/specs
diff --git a/development/gcc5/patches/glibc2.28-ustat.diff b/development/gcc5/patches/glibc2.28-ustat.diff
new file mode 100644
index 0000000000..c7d71d0677
--- /dev/null
+++ b/development/gcc5/patches/glibc2.28-ustat.diff
@@ -0,0 +1,31 @@
+--- libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc 2018/04/25 07:39:32 259630
++++ libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc 2018/05/24 20:07:25 260687
+@@ -138,7 +138,6 @@
+ # include <sys/procfs.h>
+ #endif
+ #include <sys/user.h>
+-#include <sys/ustat.h>
+ #include <linux/cyclades.h>
+ #include <linux/if_eql.h>
+ #include <linux/if_plip.h>
+@@ -231,7 +230,19 @@
+ #endif // SANITIZER_LINUX || SANITIZER_FREEBSD
+
+ #if SANITIZER_LINUX && !SANITIZER_ANDROID
+- unsigned struct_ustat_sz = sizeof(struct ustat);
++ // Use pre-computed size of struct ustat to avoid <sys/ustat.h> which
++ // has been removed from glibc 2.28.
++#if defined(__aarch64__) || defined(__s390x__) || defined (__mips64) \
++ || defined(__powerpc64__) || defined(__arch64__) || defined(__sparcv9) \
++ || defined(__x86_64__)
++#define SIZEOF_STRUCT_USTAT 32
++#elif defined(__arm__) || defined(__i386__) || defined(__mips__) \
++ || defined(__powerpc__) || defined(__s390__)
++#define SIZEOF_STRUCT_USTAT 20
++#else
++#error Unknown size of struct ustat
++#endif
++ unsigned struct_ustat_sz = SIZEOF_STRUCT_USTAT;
+ unsigned struct_rlimit64_sz = sizeof(struct rlimit64);
+ unsigned struct_statvfs64_sz = sizeof(struct statvfs64);
+ #endif // SANITIZER_LINUX && !SANITIZER_ANDROID
hi luvr,
as I reported on the other thread the glibc patch doesn't seem needed here: have you tried building this stuff on a fresh installed full installation of slackware current as requested on the first post of this thread? I suppose not...
regarding openjdk/apache-ant can you please get in touch with the openjdk maintainer and ask his opinion on the matter?
have you tried building this stuff on a fresh installed full installation of slackware current as requested on the first post of this thread?
I didn’t install a new copy of Slackware-current, if that’s what you’re asking.
To arrive at my Slackware-current system, I did a full install (as in everything—including KDE and KDEI) of Slackware 14.2, after which I fully updated this Slackware 14.2 system. I subsequently downloaded a local copy of the Slackware-current repository, and upgraded to Slackware-current from that local copy. Ever since, I keep my Slackware-current system up-to-date on average once a week.
I do run a “slackpkg clean-system” as part of my updates, so any “obsolete” packages get removed. My complete update cycle (once my local repository copy is updated) consists of the following sequence of commands:
(The ‘smp’ kernel entries are not really required, since this is a 64-bit system. There are currently no alien packages installed, and the compat32 entry is superfluous, since this is a pure 64-bit system.) New kernels get installed separately, to ensure that the running kernel won’t get removed while I’m not looking.
If you really want me to install a new Slackware-current system, I’m not, in principle, opposed to doing so, but it won’t be particularly high on my priority list. I would be interested to know if there’s anything that I could do differently, though; if I simply follow the exact same procedure as last time, I’m inclined to believe that the results will most likely be the same as well.
In any case, the patch appears relevant to me, since it mentions glibc 2.28, which no longer provides the affected header file.
An earlier remark from Pat makes me wonder if, perhaps, you somehow have a pre-compiled header file lying around somewhere, which happens to provide the contents of the file that is no longer available???
If you really want me to install a new Slackware-current system, I’m not, in principle, opposed to doing so, but it won’t be particularly high on my priority list. I would be interested to know if there’s anything that I could do differently, though; if I simply follow the exact same procedure as last time, I’m inclined to believe that the results will most likely be the same as well.
I have no idea if something had broken in your installation with usage...
you can try installing directly current using an iso
if you do a full installation and try to build gcc5 from this fork of SBo as the first action after rebooting post-installation the environment should be as clean as it can get, I suppose.
Quote:
In any case, the patch appears relevant to me, since it mentions glibc 2.28, which no longer provides the affected header file.
An earlier remark from Pat makes me wonder if, perhaps, you somehow have a pre-compiled header file lying around somewhere, which happens to provide the contents of the file that is no longer available???
as I already explained you in the other thread, I haven't got that header and the gcc5.SlackBuild I run in my freshly installed slackware current system doesn't require it during building.
I cannot see the point of starting the same discussion again in this thread...
Hmmm... Seems like an interesting option.
I have a spare disk partition on this laptop anyway, and I would be curious to find out if such an installation behaves in any way different from my current one.
try to avoid customizing the environment or anything else post-installation in any way, just run as root the gcc5.SlackBuild at the first reboot and see if it behaves the same way.
Last week I added a patch so that dwm-6.2 will build in 14.2. The patch allows it to use the fontconfig in 14.2 by undoing references to LC_COLOR in the latest dwm git commit.
This patch isn't necesary with -current and it should build without it (tested last week).
I'll remove it from the repo, thanks for notifying!
sorry dive, I've seen there seems to be two patches now, 0001-Prepare-6.2-release.patch and 0001-Prepare-6.2-release-2.patch, now but only one seems to be applied (the first): which one do you intend me to remove for current?
splix not building on current - needed for Samsung ML-1670 printer
I have a Samsung ML-1670 printer I want to move onto a new Slackware-arm current system. I am new to arm, not new to Slackware.
On 14.2 64 bit, the splix package compiles, installs and works as expected. There is a pre-req of jbigkit. It is also fine on 14.2.
On trying to solve the install problem on my new skackware arm ( 32 bit ) system, jbigkit will not compile. Here is the last few lines of the failure.
Code:
bigkit-2.1/pbmtools/pbm.txt
jbigkit-2.1/pbmtools/pgm.txt
gcc -O2 -c -o jbig.o jbig.c
gcc -O2 -c -o jbig_ar.o jbig_ar.c
rm -f libjbig.a
ar rc libjbig.a jbig.o jbig_ar.o
ranlib libjbig.a
/usr/bin/ld: jbig.o: relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: jbig_ar.o: relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: jbig.o(.text+0x1b50): unresolvable R_ARM_CALL relocation against symbol `realloc@@GLIBC_2.4'
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
Note the "recompile with fPIC".
My next attempt was to see if this was just a failure on arm, or arm and Slackware 64 current.
jbigkit compiles and install on Slack 64 current. OK, so onto splix. I ran the command sbopkg -i splix. Here is the error output.
Quote:
PRE-CHECK LOG
Using the UNSUPPORTED SBo git repository for -current
Queue Process: Download, build, and install
jbigkit:
GPG checks not supported for the SBo-git repository.
Processing jbigkit 2.1-1
Using original .info file
Using original SlackBuild file
No build options selected.
splix:
GPG checks not supported for the SBo-git repository.
Processing splix 2.0.0-2
Using original .info file
Using original SlackBuild file
No build options selected.
+++++++++++++++++++++++++++++++++++++++++++
Pre-check complete.
Do you wish to proceed based on the search results above? Packages not
found will be skipped during the process.
(P)roceed or (Q)uit?: p
Processing jbigkit
jbigkit:
Found jbigkit-2.1.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
MD5SUM check for jbigkit-2.1.tar.gz ... OK
Building package for jbigkit...
jbigkit-2.1/
jbigkit-2.1/ANNOUNCE
jbigkit-2.1/CHANGES
jbigkit-2.1/COPYING
jbigkit-2.1/INSTALL
jbigkit-2.1/Makefile
jbigkit-2.1/TODO
jbigkit-2.1/contrib/
jbigkit-2.1/contrib/INDEX
jbigkit-2.1/contrib/atariprj.tar
jbigkit-2.1/examples/
jbigkit-2.1/examples/README
jbigkit-2.1/examples/ccitt1.jbg
jbigkit-2.1/examples/ccitt2.jbg
jbigkit-2.1/examples/ccitt3.jbg
jbigkit-2.1/examples/ccitt4.jbg
jbigkit-2.1/examples/ccitt5.jbg
jbigkit-2.1/examples/ccitt6.jbg
jbigkit-2.1/examples/ccitt7.jbg
jbigkit-2.1/examples/ccitt8.jbg
jbigkit-2.1/examples/jbgtests.m
jbigkit-2.1/examples/multi.pgm
jbigkit-2.1/examples/mx.jbg
jbigkit-2.1/examples/sandra.pgm
jbigkit-2.1/examples/xvlogo.jbg
jbigkit-2.1/libjbig/
jbigkit-2.1/libjbig/Makefile
jbigkit-2.1/libjbig/jbig.c
jbigkit-2.1/libjbig/jbig.h
jbigkit-2.1/libjbig/jbig.txt
jbigkit-2.1/libjbig/jbig85.c
jbigkit-2.1/libjbig/jbig85.h
jbigkit-2.1/libjbig/jbig85.txt
jbigkit-2.1/libjbig/jbig_ar.c
jbigkit-2.1/libjbig/jbig_ar.h
jbigkit-2.1/libjbig/po/
jbigkit-2.1/libjbig/po/README.txt
jbigkit-2.1/libjbig/po/de.po
jbigkit-2.1/libjbig/po/ru.po
jbigkit-2.1/libjbig/tstcodec.c
jbigkit-2.1/libjbig/tstcodec85.c
jbigkit-2.1/pbmtools/
jbigkit-2.1/pbmtools/Makefile
jbigkit-2.1/pbmtools/jbgfuzz.pl
jbigkit-2.1/pbmtools/jbgtopbm.1
jbigkit-2.1/pbmtools/jbgtopbm.c
jbigkit-2.1/pbmtools/jbgtopbm85.c
jbigkit-2.1/pbmtools/pbm.5
jbigkit-2.1/pbmtools/pbmtojbg.1
jbigkit-2.1/pbmtools/pbmtojbg.c
jbigkit-2.1/pbmtools/pbmtojbg85.c
jbigkit-2.1/pbmtools/pgm.5
jbigkit-2.1/pbmtools/pbmtojbg.txt
jbigkit-2.1/pbmtools/jbgtopbm.txt
jbigkit-2.1/pbmtools/pbm.txt
jbigkit-2.1/pbmtools/pgm.txt
make: 'libjbig.a' is up to date.
/usr/bin/ld: jbig.o: relocation R_X86_64_32S against `.text' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: jbig_ar.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
jbigkit:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?: n
+++++++++++++++++++++++++++++++++++++++++++
SUMMARY LOG
Using the UNSUPPORTED SBo git repository for -current
Queue Process: Download, build, and install
jbigkit:
MD5SUM check for jbigkit-2.1.tar.gz ... OK
Error occurred with build. Please check the log.
Please note, jbigkit installed OK when run by itself.
What I did; I had installed jbigkit successfully. I tried to install splix, I tried to use the queue file containing two lines, jbigkit and splix. That produced the error 'recompile with fPIC' message.
I just compiled and installed splix on its own, I did not call it from the queue file. That worked, I will try to install the printer now on current 64 bit, full install and report back.
My bigger problem is I want that printer on my rasberry pi running slackware current. I want that system to be my print server. If the ML1670 printer works on current 64 bit, I will open a thread on the arm forum and see if they can help.
I tried also to run a queue with jbigkit and splix together and they built fine
Code:
+++++++++++++++++++++++++++++++++++++++++++
SUMMARY LOG
Using the UNSUPPORTED SBo git repository for -current
Queue Process: Download, build, and install
jbigkit:
MD5SUM check for jbigkit-2.1.tar.gz ... OK
Building package jbigkit-2.1-x86_64-1ponce.txz ... OK
Installing package jbigkit-2.1-x86_64-1ponce.txz ... OK
splix:
MD5SUM check for splix-2.0.0.tar.bz2 ... OK
Building package splix-2.0.0-x86_64-2ponce.txz ... OK
Installing package splix-2.0.0-x86_64-2ponce.txz ... OK
+++++++++++++++++++++++++++++++++++++++++++
###########################################
Queue process complete!
###########################################
I'm sorry but I haven't tested an installation of the scripts on slackwarearm-current, as I don't have it available ATM...
Probably already known, but virtualbox requires virtualbox-kernel, which does not build on -current:
Code:
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciLinuxDevDetachHostDriver’:
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:92:40: error: implicit declaration of function ‘pci_get_bus_and_slot’; did you mean ‘pci_get_domain_bus_and_slot’? [-Werror=implicit-function-declaration]
# define PCI_DEV_GET_SLOT(bus, devfn) pci_get_bus_and_slot(bus, devfn)
^~~~~~~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:397:15: note: in expansion of macro ‘PCI_DEV_GET_SLOT’
pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn);
^~~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:397:13: warning: assignment to ‘struct pci_dev *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn);
^
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciOsDevInit’:
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:648:17: warning: assignment to ‘struct pci_dev *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
pPciDev = PCI_DEV_GET_SLOT((pIns->HostPciAddress) >> 8,
^
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:303: /tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.o] Error 1
make[2]: *** [Makefile:1525: _module_/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci] Error 2
make[2]: Leaving directory '/usr/src/linux-4.19.34'
make[1]: *** [/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/Makefile.include.footer:101: vboxpci] Error 2
make[1]: Leaving directory '/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci'
make: *** [Makefile:54: all] Error 1
It looks like they changed some calls between kernel 4.14.x and 4.19.x?
I don't know what it would take to bump the version as it looks like anything after 5.2.10 doesn't have a virtualbox-kernel source anymore.
Probably already known, but virtualbox requires virtualbox-kernel, which does not build on -current:
Code:
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciLinuxDevDetachHostDriver’:
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:92:40: error: implicit declaration of function ‘pci_get_bus_and_slot’; did you mean ‘pci_get_domain_bus_and_slot’? [-Werror=implicit-function-declaration]
# define PCI_DEV_GET_SLOT(bus, devfn) pci_get_bus_and_slot(bus, devfn)
^~~~~~~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:397:15: note: in expansion of macro ‘PCI_DEV_GET_SLOT’
pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn);
^~~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:397:13: warning: assignment to ‘struct pci_dev *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn);
^
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciOsDevInit’:
/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c:648:17: warning: assignment to ‘struct pci_dev *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
pPciDev = PCI_DEV_GET_SLOT((pIns->HostPciAddress) >> 8,
^
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:303: /tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.o] Error 1
make[2]: *** [Makefile:1525: _module_/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci] Error 2
make[2]: Leaving directory '/usr/src/linux-4.19.34'
make[1]: *** [/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci/Makefile.include.footer:101: vboxpci] Error 2
make[1]: Leaving directory '/tmp/SBo/virtualbox-kernel-5.2.8/vboxpci'
make: *** [Makefile:54: all] Error 1
It looks like they changed some calls between kernel 4.14.x and 4.19.x?
I don't know what it would take to bump the version as it looks like anything after 5.2.10 doesn't have a virtualbox-kernel source anymore.
try patching the virtualbox-kernel.SlackBuild for 5.2.8 with this
Code:
From 4336ad1132c00a189ea38bd8330cce8a51457af5 Mon Sep 17 00:00:00 2001
From: Matteo Bernardini <ponce@slackbuilds.org>
Date: Tue, 16 Apr 2019 23:22:24 +0200
Subject: [PATCH] system/virtualbox-kernel: Patch for kernel >= 4.17.x.
Signed-off-by: Matteo Bernardini <ponce@slackbuilds.org>
---
system/virtualbox-kernel/kernel_4.17.patch | 32 +++++++++++++++++++
.../virtualbox-kernel.SlackBuild | 2 ++
2 files changed, 34 insertions(+)
create mode 100644 system/virtualbox-kernel/kernel_4.17.patch
diff --git a/system/virtualbox-kernel/kernel_4.17.patch b/system/virtualbox-kernel/kernel_4.17.patch
new file mode 100644
index 0000000000..007bf737f2
--- /dev/null
+++ b/system/virtualbox-kernel/kernel_4.17.patch
@@ -0,0 +1,32 @@
+In kernel 4.17, pci_get_bus_and_slot() has been removed in favor of
+pci_get_domain_bus_and_slot(). It appears that VirtualBox only uses
+domain number 0, thus pci_get_domain_bus_and_slot(0, bus, devfn)
+is a suitable replacement for pci_get_bus_and_slot(bus, devfn).
+
+The resulting code compiles; however, I do not use PCI passthru, which
+I think means that I have not actually tested the code.
+
+This patch released under a combined MIT/GPLv2 license.
+
+Shamelessly stolen from the patch by Larry Finger.
+
+Signed-off-by: Matteo Bernardini <ponce@slackbuilds.org>
+
+diff -Naur virtualbox-kernel-5.2.8.orig/vboxpci/linux/VBoxPci-linux.c virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c
+--- virtualbox-kernel-5.2.8.orig/vboxpci/linux/VBoxPci-linux.c 2018-03-14 20:33:31.000000000 +0100
++++ virtualbox-kernel-5.2.8/vboxpci/linux/VBoxPci-linux.c 2019-04-16 23:18:10.607698000 +0200
+@@ -89,7 +89,14 @@
+ #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 20)
+ # define PCI_DEV_GET(v,d,p) pci_get_device(v,d,p)
+ # define PCI_DEV_PUT(x) pci_dev_put(x)
++#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 17, 0)
++/* assume the domain number to be zero - exactly the same assumption of
++* pci_get_bus_and_slot()
++*/
++# define PCI_DEV_GET_SLOT(bus, devfn) pci_get_domain_bus_and_slot(0, bus, devfn)
++#else
+ # define PCI_DEV_GET_SLOT(bus, devfn) pci_get_bus_and_slot(bus, devfn)
++#endif
+ #else
+ # define PCI_DEV_GET(v,d,p) pci_find_device(v,d,p)
+ # define PCI_DEV_PUT(x) do { } while (0)
diff --git a/system/virtualbox-kernel/virtualbox-kernel.SlackBuild b/system/virtualbox-kernel/virtualbox-kernel.SlackBuild
index 21b57d9a53..338da42bfc 100644
--- a/system/virtualbox-kernel/virtualbox-kernel.SlackBuild
+++ b/system/virtualbox-kernel/virtualbox-kernel.SlackBuild
@@ -84,6 +84,8 @@ if [ "$KERNEL_MINOR" = 4 -a "$KERNEL_PATCH" -ge 168 ]; then
sed -i "s|KERNEL_VERSION(4, 9, 0)|KERNEL_VERSION(4, 4, 168)|" vboxdrv/r0drv/linux/memobj-r0drv-linux.c
fi
+patch -p1 < $CWD/kernel_4.17.patch
+
make KERN_DIR=${KERNELPATH}
mkdir -p $PKG/lib/modules/$KERNEL/misc
--
2.21.0
Last week I added a patch so that dwm-6.2 will build in 14.2. The patch allows it to use the fontconfig in 14.2 by undoing references to LC_COLOR in the latest dwm git commit.
This patch isn't necesary with -current and it should build without it (tested last week).
I'll remove it from the repo, thanks for notifying!
sorry dive, I've seen there seems to be two patches now, 0001-Prepare-6.2-release.patch and 0001-Prepare-6.2-release-2.patch, now but only one seems to be applied (the first): which one do you intend me to remove for current?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
