The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
The SUBDIRS variable has been removed in kernel 5.4, and was deprecated
since the beginnig of kernel git history in favour of M or KBUILD_EXTMOD.
Signed-off-by: David Bauer <mail@david-bauer.net>
Patches require a bit of rework:
- dropped 010-missing-header.patch
- add 010-do-not-run-test-progs.patch
- re-updated 020-filterh-use-host-built-version.patch
- Makefile.in gets regenerated from PKG_FIXUP:=autoreconf
- added PKG_FIXUP:=autoreconf ; it's easier to patch automake stuff that
big configure scripts
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* Added optional ipv4 resolvers UCI config option
* Added logging to logd
* Refactored verbosity UCI config option
* Filtered out any address from being added to dnsmasq
Signed-off-by: Gerard Ryan <G.M0N3Y.2503@gmail.com>
If libacl is built, gnu sed finds it during configuration and enables support
linking in libacl. This results in build failures due to the missing dependency.
Consequently, use CONFIGURE_ARGS to disable acl support.
Reported-by: Rosen Penev rosenp@gmail.com
Signed-off-by: Russell Senior <russell@personaltelco.net>
Compilation is broken on AArch64.
Reordered some things for consistency between packages.
Fixed license information.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
The previous implementation always succeeded so no scan was performed.
This now fixes that and it correctly scans for BTRFS devices if BTRFS
support is in kernel.
Signed-off-by: Karel Kočí <karel.koci@nic.cz>
exFAT fs driver has been upstreamed as a staging driver since linux 5.4.
The package name kmod-fs-exfat is used for that.
Three things happened in this commit
- The package will only be built for kernel 4.14 and 4.19
- The driver will be available as opkg package "kmod-fs-exfat0".
"kmod-fs-exfat" is to be used for the one in upstream kernel
- Mark "kmod-fs-exfat0" as deprecated in package title
Signed-off-by: Paul Blazejowski <paulb at blazebox.homeip.net>
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
(rename, rewording, and deprecation)
- Bump version also in the config file
- Move logread to /sbin location instead of /usr/sbin
Because package logd in OpenWrt's ubox Makefile uses /sbin folder and LuCI has
the same path hardcoded in
modules/luci-base/root/usr/share/rpcd/acl.d/luci-base.json and using
different location results that LuCI is not able to load log data as it
is not found.
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
While at it making it as well kernel 5.4 compatible by backporting
upstream patch which synchronizes channel types and modifier lists in
the headers.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
* The Makefile creates two packages:
- chicken-scheme-interpreter, same that was created
with the previous version of the Makefile (except
that this one includs Chicken 5.2.0);
- chicken-scheme-full, which includes the compiler,
debugger, profiler, and module manager.
The -full package has some peculiarities:
It is somewhat large, although that is not really
an issue, since it depends on gcc, which already needs
more than 100Mb space.
The binaries are not stripped, because stripped binaries
seem to break the compiler (generated objects are not
properly linked). Since the package is large and depends
on an even larger one, this shouldn't be a problem.
Signed-off-by: Jeronimo Pellegrini <j_p@aleph0.info>