Because of the lib prefix, it's not getting substituted properly and
breaks compilation of other packages.
Fixes error with at least btrfs-progs:
Package '@LIBSELINUX@', required by 'mount', not found
Package '@LIBCRYPTSETUP@', required by 'mount', not foun
Signed-off-by: Rosen Penev
---
Hi,
The OpenWrt community is proud to announce the sixth service release of
OpenWrt 19.07. It focuses on fixing several security issues.
Main changes from OpenWrt 19.07.5
Security fixes
* Security Advisory 2021-01-19-1 - dnsmasq multiple vulnerabilities
(CVE-2020-25681, CVE-2020-25682,
Use `$(AUTORELEASE)` variable rather than setting a PKG_RELEASE
on every commit manually.
Signed-off-by: Paul Spooren
---
package/boot/uboot-envtools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/boot/uboot-envtools/Makefile
The newly added `$(COMMITCOUNT)` varialbe allows automatic versioning
based on the number of Git commits of a package. Replace *tedious to
bump* and *merge conflict causing* `PKG_RELEASE` and replace it with
`$(COMMITCOUNT)`.
Signed-off-by: Paul Spooren
---
package/base-files/Makefile | 2 +-
1
Use `$(AUTORELEASE)` variable rather than setting a PKG_RELEASE
on every commit manually.
Signed-off-by: Paul Spooren
---
package/utils/busybox/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/utils/busybox/Makefile b/package/utils/busybox/Makefile
index
The lack of bumped PKG_RELEASE variables is a recurring theme on the
mailing list and in GitHub comments. This costs precious review time,
a rare good within the OpenWrt project.
Instead of relying on a manually set PKG_RELEASE this commit adds a
`commitcount` function that uses the number of Git
DESCRIPTION
Dnsmasq has two sets of vulnerabilities, one set of memory corruption issues
handling DNSSEC and a second set of issues validating DNS responses. These
vulnerabilities could allow an attacker to corrupt memory on the target device
and perform cache poisoning attacks against the target
DESCRIPTION
Dnsmasq has two sets of vulnerabilities, one set of memory corruption issues
handling DNSSEC and a second set of issues validating DNS responses. These
vulnerabilities could allow an attacker to corrupt memory on the target device
and perform cache poisoning attacks against the target
The majority of our targets provide a default value for the variable
SUPPORTED_DEVICES, which is used in images to check against the
compatible on a running device:
SUPPORTED_DEVICES := $(subst _,$(comma),$(1))
At the moment, this is implemented in the Device/Default block of
the individual
> It should be possible to make final defines even simpler by using some
> wildcard magic. You could avoid defining SOC then.
>
> Please take a look at the:
> target/linux/bcm53xx/image/Makefile
>
> It has some magic² code as follows:
> DEVICE_DTS := $(patsubst %.dtb,%,$(notdir $(wildcard $(if
>
On 19.01.2021 19:53, Adrian Schmutzler wrote:
This sets the DTS paths automatically based on their device definition
name. Devices where this is not possible may still be served by simply
overwriting DEVICE_DTS in their respective definition.
Cc: Rafał Miłecki
Signed-off-by: Adrian Schmutzler
This sets the DTS paths automatically based on their device definition
name. Devices where this is not possible may still be served by simply
overwriting DEVICE_DTS in their respective definition.
Cc: Rafał Miłecki
Signed-off-by: Adrian Schmutzler
---
Of course, any paths which are not
> -Original Message-
> From: Rafał Miłecki [mailto:ra...@milecki.pl]
> Sent: Dienstag, 19. Januar 2021 19:09
> To: Adrian Schmutzler
> Cc: 'Rafał Miłecki' ; openwrt-devel@lists.openwrt.org;
> nolt...@gmail.com
> Subject: Re: [PATCH 2/2] bcm4908: build flashable & bootable firmware
>
On 2021-01-19 12:32, Adrian Schmutzler wrote:
> cp $(KDIR)/bcm63xx-cfe/$(subst
_,$(comma),$(DEVICE_NAME))/cferam.000
> $@-bootfs/
>
> This will remove the additional variable by simply making the current
> soft rule to have matching device definition name and compatible a
> hard one.
Are you
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Switch to normal tarballs for
Hi,
due to a recent discussion on bcm4908 target, I became aware of the naming
scheme for (device) directories in bcm63xx-cfe, which is based on a device's
compatible.
Since these packages are used during _build_, it seems a bit odd to use the
compatible here, as it's a variable used on the
Hi Peter, Bjorn,
Op woensdag 13 januari 2021 om 18u43 schreef Sander Vanheule
:
Hi,
On Mon, 2020-11-30 at 23:19 +0100, Bjørn Mork wrote:
Bjørn Mork (10):
dt-bindings: mtd: partitions: add OpenWrt defined U-Boot Image
kernel: mtdsplit_uimage: read extralen from device tree
kernel:
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Rafal Milecki
> Sent: Montag, 18. Januar 2021 12:42
> To: Adrian Schmutzler
> Cc: 'Rafał Miłecki' ; nolt...@gmail.com; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [PATCH 2/2]
> > cp $(KDIR)/bcm63xx-cfe/$(subst
> _,$(comma),$(DEVICE_NAME))/cferam.000
> > $@-bootfs/
> >
> > This will remove the additional variable by simply making the current
> > soft rule to have matching device definition name and compatible a
> > hard one.
>
> Are you still planning on adding generic
On Mon, Jan 18, 2021 at 11:27 PM Sergey Ponomarev wrote:
>
> When installing rpcd directly from CMake then the file is missing.
>
> Signed-off-by: Sergey Ponomarev
Reviewed-by: Rosen Penev
> ---
> CMakeLists.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/CMakeLists.txt
On Mon, Jan 18, 2021 at 11:21 PM Sergey Ponomarev wrote:
>
> The cmake logic is wrong (E.G. PKG_CHECK_FOR_MODULES fails unless all modules
> are found), and the legacy libjson.so name is also used by the other libjson
> (http://sourceforge.net/projects/libjson/) which provides an incompatible
21 matches
Mail list logo
