Re: [PATCH] build: SDK/IB reproducible and faster compression
As friends of reproducible builds please have a look at this patch. On 13.08.20 13:46, Paul Spooren wrote: Both IB and SDK now use the same logic for packing. This commit add reproducible multithread compression to the SDK and corrects the file mtime for both. Previously all files where just copied over from the build system, generating random mtimes. Signed-off-by: Paul Spooren --- This speeds up SDK building on my machine by 4x. target/imagebuilder/Makefile | 5 - target/sdk/Makefile | 3 ++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/target/imagebuilder/Makefile b/target/imagebuilder/Makefile index b463feb456..ad19ab2b53 100644 --- a/target/imagebuilder/Makefile +++ b/target/imagebuilder/Makefile @@ -86,7 +86,10 @@ endif (cd $(PKG_BUILD_DIR); find staging_dir/host/bin/ $(IB_LDIR)/scripts/dtc/ -type f | \ $(XARGS) $(SCRIPT_DIR)/bundle-libraries.sh $(PKG_BUILD_DIR)/staging_dir/host) STRIP=sstrip $(SCRIPT_DIR)/rstrip.sh $(PKG_BUILD_DIR)/staging_dir/host/bin/ - $(TAR) -cf - -C $(BUILD_DIR) $(IB_NAME) | xz -T$(if $(filter 1,$(NPROC)),2,0) -zc -7e > $@ + (cd $(BUILD_DIR); \ + tar -I '$(STAGING_DIR_HOST)/bin/xz -7e -T$(if $(filter 1,$(NPROC)),2,0)' -cf $@ $(IB_NAME) \ + --mtime="$(shell date --date=@$(SOURCE_DATE_EPOCH))"; \ + ) download: prepare: diff --git a/target/sdk/Makefile b/target/sdk/Makefile index d3552b47eb..022a791ebf 100644 --- a/target/sdk/Makefile +++ b/target/sdk/Makefile @@ -152,7 +152,8 @@ $(BIN_DIR)/$(SDK_NAME).tar.xz: clean find $(SDK_BUILD_DIR) -name CVS | $(XARGS) rm -rf -make -C $(SDK_BUILD_DIR)/scripts/config clean (cd $(BUILD_DIR); \ - tar -I 'xz -7e' -cf $@ $(SDK_NAME); \ + tar -I '$(STAGING_DIR_HOST)/bin/xz -7e -T$(if $(filter 1,$(NPROC)),2,0)' -cf $@ $(SDK_NAME) \ + --mtime="$(shell date --date=@$(SOURCE_DATE_EPOCH))"; \ ) download: ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] build: add whatdepends target to imagebuilder
The package manager `opkg` offers the function `whatdepends` to print packages that depend on a specific package. This feature is useful when used in a CI to not only build an upgraded package but all packages with a dependency. Usage: make whatdepends PACKAGE=libipset The resulting list can be fed into a SDK building all packages and warn if anything fails. Signed-off-by: Paul Spooren --- I'm currently running a CI which determines affected areas as first step, an example is here where the `fstools` packages was modified: https://gitlab.com/aparcar/openwrt/-/jobs/696713593#L48 With the whatdepends extension it would be possible to figure out all affected packages. target/imagebuilder/files/Makefile | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/target/imagebuilder/files/Makefile b/target/imagebuilder/files/Makefile index 326dd2ba2f..27d3cfa8df 100644 --- a/target/imagebuilder/files/Makefile +++ b/target/imagebuilder/files/Makefile @@ -220,4 +220,12 @@ manifest: FORCE $(if $(PROFILE),USER_PROFILE="$(PROFILE_FILTER)") \ $(if $(PACKAGES),USER_PACKAGES="$(PACKAGES)")) -.SILENT: help info image manifest +whatdepends: FORCE +ifeq ($(PACKAGE),) + @echo 'Variable `PACKAGE` is not set but required by `whatdepends`' + @exit 1 +endif + @$(MAKE) -s package_reload + @$(OPKG) whatdepends -A $(PACKAGE) + +.SILENT: help info image manifest whatdepends -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2 2/2] pistachio: use generic diag.sh
Remove local diag.sh in favor of generic one and add the required
led-* aliases to DTS.
Signed-off-by: Adrian Schmutzler
---
target/linux/pistachio/base-files/etc/diag.sh | 30 ---
...-MIPS-DTS-img-marduk-Add-led-aliases.patch | 27 +
2 files changed, 27 insertions(+), 30 deletions(-)
delete mode 100755 target/linux/pistachio/base-files/etc/diag.sh
create mode 100644
target/linux/pistachio/patches-5.4/905-MIPS-DTS-img-marduk-Add-led-aliases.patch
diff --git a/target/linux/pistachio/base-files/etc/diag.sh
b/target/linux/pistachio/base-files/etc/diag.sh
deleted file mode 100755
index ed69d43385..00
--- a/target/linux/pistachio/base-files/etc/diag.sh
+++ /dev/null
@@ -1,30 +0,0 @@
-#!/bin/sh
-#
-# Copyright (C) 2017 OpenWrt.org
-#
-# This is free software, licensed under the GNU General Public License v2.
-# See /LICENSE for more information.
-#
-
-. /lib/functions/leds.sh
-
-status_led="marduk:red:heartbeat"
-
-set_state() {
-
- case "$1" in
- preinit)
- status_led_blink_preinit
- ;;
- failsafe)
- status_led_blink_failsafe
- ;;
- upgrade | \
- preinit_regular)
- status_led_blink_preinit_regular
- ;;
- done)
- status_led_on
- ;;
- esac
-}
diff --git
a/target/linux/pistachio/patches-5.4/905-MIPS-DTS-img-marduk-Add-led-aliases.patch
b/target/linux/pistachio/patches-5.4/905-MIPS-DTS-img-marduk-Add-led-aliases.patch
new file mode 100644
index 00..c6cf5acbb8
--- /dev/null
+++
b/target/linux/pistachio/patches-5.4/905-MIPS-DTS-img-marduk-Add-led-aliases.patch
@@ -0,0 +1,27 @@
+--- a/arch/mips/boot/dts/img/pistachio_marduk.dts
b/arch/mips/boot/dts/img/pistachio_marduk.dts
+@@ -19,6 +19,11 @@
+ ethernet0 =
+ spi0 =
+ spi1 =
++
++ led-boot = _heartbeat;
++ led-failsafe = _heartbeat;
++ led-running = _heartbeat;
++ led-upgrade = _heartbeat;
+ };
+
+ chosen {
+@@ -88,11 +93,10 @@
+
+ leds {
+ compatible = "pwm-leds";
+- heartbeat {
++ led_heartbeat: heartbeat {
+ label = "marduk:red:heartbeat";
+ pwms = < 3 30>;
+ max-brightness = <255>;
+- linux,default-trigger = "heartbeat";
+ };
+ };
+
--
2.20.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2 1/2] pistachio: use vendor_model scheme for device/image name
This uses the vendor_model scheme for the device/image name in order to make this consistent to most other targets. Signed-off-by: Adrian Schmutzler --- target/linux/pistachio/image/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/target/linux/pistachio/image/Makefile b/target/linux/pistachio/image/Makefile index 61f5c55237..278027ce20 100644 --- a/target/linux/pistachio/image/Makefile +++ b/target/linux/pistachio/image/Makefile @@ -23,7 +23,7 @@ define Device/Default IMAGE/sysupgrade.tar := sysupgrade-tar endef -define Device/marduk +define Device/img_creator-ci40 DEVICE_VENDOR := Imagination Technologies DEVICE_MODEL := Creator Ci40 (VL-62899) DEVICE_ALT0_VENDOR := Imagination Technologies @@ -35,7 +35,7 @@ define Device/marduk DEVICE_PACKAGES := kmod-tpm-i2c-infineon endef -TARGET_DEVICES += marduk +TARGET_DEVICES += img_creator-ci40 $(eval $(call BuildImage)) -- 2.20.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH 19.07] tools/tplink-safeloader: use soft_ver 1.9.1 for archer c6 v2
From: Alexander Couzens
TP-LINK published a firmware update for the archer c6 v2.
This updates also reached the factory devices. Newer software version
rejects downgrading to 1.2.x. Use 1.9.x to allow installing the factory images
and have a little bit time to change it again.
Tested on archer c6 v2 with firmware 1.3.1
Signed-off-by: Alexander Couzens
(cherry picked from commit 6d5d815e3f6850a0dc754bf16053fa34490766f7)
[remove changes to C6-V2-US because it's unsupported in 19.07]
Signed-off-by: Baptiste Jonglez
---
tools/firmware-utils/src/tplink-safeloader.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/firmware-utils/src/tplink-safeloader.c
b/tools/firmware-utils/src/tplink-safeloader.c
index 08e21e74e3..e4f11bf4c8 100644
--- a/tools/firmware-utils/src/tplink-safeloader.c
+++ b/tools/firmware-utils/src/tplink-safeloader.c
@@ -710,7 +710,7 @@ static struct device_info boards[] = {
"{product_name:Archer
C6,product_ver:2.0.0,special_id:5255}\r\n"
"{product_name:Archer
C6,product_ver:2.0.0,special_id:4A50}\r\n",
.support_trail = '\x00',
- .soft_ver = "soft_ver:1.1.1\n",
+ .soft_ver = "soft_ver:1.9.1\n",
.partitions = {
{"fs-uboot", 0x0, 0x2},
--
2.27.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: Announcement: Removal of 4.14 kernel from master
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Mauro Mozzarelli
> Sent: Donnerstag, 20. August 2020 16:08
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: Announcement: Removal of 4.14 kernel from master
>
> Why is ar71xx no longer going to be supported?
>
> This includes Netgear WNDR-3700-v4 which is a very popular and reliable
> router in the OpenWRT community.
ar71xx has been supposed to be replaced by ath79 for quite a long time already.
19.07 is the last release to include the old ar71xx, which is why we made the
target source-only after that. As many others, the WNDR3700 v4 has already been
ported to ath79, so you would just take the ath79 image then.
Best
Adrian
>
>
> On 20/08/2020 14:32, Adrian Schmutzler wrote:
> > Hi all,
> >
> > I've sent a few reminders about this topic already, and in yesterday's
> > virtual
> meeting we decided to finally remove the 4.14 kernel support in master
> _before_ branching a 20.xx branch.
> >
> > Therefore, I announce that the support for 4.14 as well as the following
> targets not updated beyond this version will be removed from master in
> _two weeks_:
> >
> > ar71xx
> > at91
> > ath25
> > rb532
> > samsung
> > uml
> >
> > The corresponding patchset is already available for illustration here (same
> patches, just two different platforms):
> >
> https://git.openwrt.org/?p=openwrt/staging/adrian.git;a=shortlog;h=refs/h
> eads/remove414
> > https://github.com/adschm/openwrt/commits/remove414
> >
> > If somebody wants to upgrade one of the named targets to 5.4 to prevent
> it from being removed, now is your last chance!
> >
> > ("Recent" committers to the targets in Cc.)
> >
> > Best
> >
> > Adrian
> >
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
openpgp-digital-signature.asc
Description: PGP signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Announcement: Removal of 4.14 kernel from master
Hi, > Why is ar71xx no longer going to be supported? because development shifted towards the upstream-approved and device tree based ath79 target. > This includes Netgear WNDR-3700-v4 which is a very popular and reliable router > in the OpenWRT community. The Netgear WNDR-3700-v4 is supported by the ath79 target. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Announcement: Removal of 4.14 kernel from master
Why is ar71xx no longer going to be supported?
This includes Netgear WNDR-3700-v4 which is a very popular and reliable
router in the OpenWRT community.
On 20/08/2020 14:32, Adrian Schmutzler wrote:
Hi all,
I've sent a few reminders about this topic already, and in yesterday's virtual
meeting we decided to finally remove the 4.14 kernel support in master _before_
branching a 20.xx branch.
Therefore, I announce that the support for 4.14 as well as the following
targets not updated beyond this version will be removed from master in _two
weeks_:
ar71xx
at91
ath25
rb532
samsung
uml
The corresponding patchset is already available for illustration here (same
patches, just two different platforms):
https://git.openwrt.org/?p=openwrt/staging/adrian.git;a=shortlog;h=refs/heads/remove414
https://github.com/adschm/openwrt/commits/remove414
If somebody wants to upgrade one of the named targets to 5.4 to prevent it from
being removed, now is your last chance!
("Recent" committers to the targets in Cc.)
Best
Adrian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Merged: options: fix parsing of boolean attributes
Merged into project/firewall3.git, branch master at http://git.openwrt.org/?p=project/firewall3.git. Thank you! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Announcement: Removal of 4.14 kernel from master
Hi all,
I've sent a few reminders about this topic already, and in yesterday's virtual
meeting we decided to finally remove the 4.14 kernel support in master _before_
branching a 20.xx branch.
Therefore, I announce that the support for 4.14 as well as the following
targets not updated beyond this version will be removed from master in _two
weeks_:
ar71xx
at91
ath25
rb532
samsung
uml
The corresponding patchset is already available for illustration here (same
patches, just two different platforms):
https://git.openwrt.org/?p=openwrt/staging/adrian.git;a=shortlog;h=refs/heads/remove414
https://github.com/adschm/openwrt/commits/remove414
If somebody wants to upgrade one of the named targets to 5.4 to prevent it from
being removed, now is your last chance!
("Recent" committers to the targets in Cc.)
Best
Adrian
openpgp-digital-signature.asc
Description: PGP signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] options: fix parsing of boolean attributes
On 19/08/2020 21:34, Rémi NGUYEN VAN wrote: I see this is getting mixed with other patches, so to be clear this is a patch for firewall3 (see https://bugs.openwrt.org/index.php?do=details_id=3284). Let me know if there is a better place to post this. Use "[PATCH] fw3: " (or "firewall3: ...") as the subject when sending the patch, and try to ensure the firewall3 maintainers, if any, are copied (email CC). You get that information from previous patches to firewall3 (look at the commit logs in git that touch the firewall3 directories) and from firewall3's OpenWrt Makefile. That enhances the selected visibility of the patch to the people who would act on it faster. It is also the best-practice on most of the FLOSS codebases that are complex enough to have several maintainers, subsystems, or components (examples are "git" itself, the Linux kernel, and OpenWrt :-) ). Also, since there is a bug report open about it, it is a good idea to attach the patch there. This helps ensure it won't be lost, although hopefully it will be acted upon soon enough. Please consider re-sending the patch with the subject line change I suggested (and the extra CCs to firewall3 maintainers) if nobody replies to you about it in the next two or three days. -- Henrique de Moraes Holschuh www.nic.br ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH V2 rpc] rc: new ubus object for handling /etc/init.d/ scripts
From: Rafał Miłecki
This commit adds "rc" ubus object with methods "list" and "exec" for
listing and calling init.d script appropriately. It's useful for all
kind of UIs (e.g. LuCI) and custom apps.
Example:
root@OpenWrt:~# ubus call rc list
{
"blockd": {
"enabled": true,
"running": true
},
"dnsmasq": {
"enabled": true,
"running": true
}
}
root@OpenWrt:~# ubus call rc init '{ "name": "blockd", "action": "disable" }'
root@OpenWrt:~# ubus call rc init '{ "name": "dnsmasq", "action": "stop" }'
root@OpenWrt:~# ubus call rc list
{
"blockd": {
"enabled": false,
"running": true
},
"dnsmasq": {
"enabled": true,
"running": false
}
}
Signed-off-by: Rafał Miłecki
---
V2: Use ubus_defer_request() and uloop_process_add() when callinig
init.d scripts. It's required as rpcd is single thread so waitpid()
could stop it from processing requests initiaited by init.d scripts.
Add timer to kill hanging init.d calls.
---
CMakeLists.txt| 2 +-
include/rpcd/rc.h | 7 +
main.c| 6 +-
rc.c | 336 ++
4 files changed, 348 insertions(+), 3 deletions(-)
create mode 100644 include/rpcd/rc.h
create mode 100644 rc.c
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3bfc286..26e011e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -38,7 +38,7 @@ INCLUDE_DIRECTORIES(${ubus_include_dir})
FIND_PATH(ubox_include_dir libubox/blobmsg_json.h)
INCLUDE_DIRECTORIES(${ubox_include_dir})
-ADD_EXECUTABLE(rpcd main.c exec.c session.c uci.c plugin.c)
+ADD_EXECUTABLE(rpcd main.c exec.c session.c uci.c rc.c plugin.c)
TARGET_LINK_LIBRARIES(rpcd ${ubox} ${ubus} ${uci} ${blobmsg_json} ${json}
${crypt} dl)
SET(PLUGINS "")
diff --git a/include/rpcd/rc.h b/include/rpcd/rc.h
new file mode 100644
index 000..ca00f56
--- /dev/null
+++ b/include/rpcd/rc.h
@@ -0,0 +1,7 @@
+// SPDX-License-Identifier: ISC OR MIT
+#ifndef __RPCD_RC_H
+#define __RPCD_RC_H
+
+int rpc_rc_api_init(struct ubus_context *ctx);
+
+#endif
diff --git a/main.c b/main.c
index 9a177cf..d77a814 100644
--- a/main.c
+++ b/main.c
@@ -25,10 +25,11 @@
#include
#include
+#include
+#include
+#include
#include
#include
-#include
-#include
static struct ubus_context *ctx;
static bool respawn = false;
@@ -113,6 +114,7 @@ int main(int argc, char **argv)
rpc_session_api_init(ctx);
rpc_uci_api_init(ctx);
+ rpc_rc_api_init(ctx);
rpc_plugin_api_init(ctx);
hangup = getenv("RPC_HANGUP");
diff --git a/rc.c b/rc.c
new file mode 100644
index 000..46407ae
--- /dev/null
+++ b/rc.c
@@ -0,0 +1,336 @@
+// SPDX-License-Identifier: ISC OR MIT
+/*
+ * rpcd - UBUS RPC server
+ *
+ * Copyright (C) 2020 Rafał Miłecki
+ */
+
+#include
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+#include
+
+#include
+
+#define RC_LIST_EXEC_TIMEOUT_MS3000
+
+enum {
+ RC_INIT_NAME,
+ RC_INIT_ACTION,
+ __RC_INIT_MAX
+};
+
+static const struct blobmsg_policy rc_init_policy[] = {
+ [RC_INIT_NAME] = { "name", BLOBMSG_TYPE_STRING },
+ [RC_INIT_ACTION] = { "action", BLOBMSG_TYPE_STRING },
+};
+
+struct rc_list_context {
+ struct uloop_process process;
+ struct uloop_timeout timeout;
+ struct ubus_context *ctx;
+ struct ubus_request_data req;
+ struct blob_buf *buf;
+ DIR *dir;
+
+ /* Info about currently processed init.d entry */
+ struct {
+ char path[PATH_MAX];
+ const char *d_name;
+ bool enabled;
+ bool running;
+ } entry;
+};
+
+static void rc_list_readdir(struct rc_list_context *c);
+
+/**
+ * rc_check_script - check if script is safe to execute as root
+ *
+ * Check if it's owned by root and if only root can modify it.
+ */
+static int rc_check_script(const char *path)
+{
+ struct stat s;
+
+ if (stat(path, ))
+ return UBUS_STATUS_NOT_FOUND;
+
+ if (s.st_uid != 0 || s.st_gid != 0 || !(s.st_mode & S_IXUSR) ||
(s.st_mode & S_IWOTH))
+ return UBUS_STATUS_PERMISSION_DENIED;
+
+ return UBUS_STATUS_OK;
+}
+
+static void rc_list_add_table(struct rc_list_context *c)
+{
+ void *e;
+
+ e = blobmsg_open_table(c->buf, c->entry.d_name);
+
+ blobmsg_add_u8(c->buf, "enabled", c->entry.enabled);
+ blobmsg_add_u8(c->buf, "running", c->entry.running);
+
+ blobmsg_close_table(c->buf, e);
+}
+
+static void rpc_list_exec_timeout_cb(struct uloop_timeout *t)
+{
+ struct rc_list_context *c = container_of(t, struct rc_list_context,
timeout);
+
+ ULOG_WARN("Timeout waiting for %s\n", c->entry.path);
+
+ uloop_process_delete(>process);
+ kill(c->process.pid, SIGKILL);
+
+ rc_list_readdir(c);
+}
+
Re: Licensing an OpenWrt router - No response to Trademark use
Hi Scott, On 19.08.2020 23:57, Heppler, J. Scott wrote: Too much effort to say "No interest at this time?" I agree, we do have problem answering e-mails from contact@ inbox. But I hope we will soon sort it out and get better at it. -- Cheers, Piotr On Aug 19, 2020: 23:25, Piotr Dymacz wrote: Hi Scott, On 18.08.2020 23:27, Heppler, J. Scott wrote: request. Reply-To: Organization: I sent an email to cont...@openwrt.org, subject line Trademark Use Request, inquiring about crowd funding an OpenWrt router. I never received a reply. The email gave the background, links to forum discussion and a poll and outlined the basic structure. The contents: Probably nobody with access to this mailbox was interested in your idea. [...] Would the project be interested in exploring this further?" Personally, I don't think so. 3y ago we (some of devs with commit access) were discussing similar idea. But there just wasn't enough interest in it. -- Cheers, Piotr ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Licensing an OpenWrt router - No response to Trademark use
On 19.08.20 23:25, Piotr Dymacz wrote: Hi Scott, On 18.08.2020 23:27, Heppler, J. Scott wrote: request. Reply-To: Organization: I sent an email to cont...@openwrt.org, subject line Trademark Use Request, inquiring about crowd funding an OpenWrt router. I never received a reply. The email gave the background, links to forum discussion and a poll and outlined the basic structure. The contents: Probably nobody with access to this mailbox was interested in your idea. [...] Would the project be interested in exploring this further?" Personally, I don't think so. 3y ago we (some of devs with commit access) were discussing similar idea. But there just wasn't enough interest in it. OpenWrt is a software project, setting up a HW supply chain would imho eat way too much time and resources. there are already thousands of routers running OpenWrt and several open HW projects making use of OpenWrt. my 2 cents John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] tools: always create $STAGING_DIR/usr/{include,lib}
rules.mk always passes these as -I/-L to the toolchain. Fixes rare errors like: cc1: error: staging_dir/target-aarch64_cortex-a53_musl/usr/include: No such file or directory [-Werror=missing-include-dirs] Signed-off-by: Andre Heider --- tools/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/Makefile b/tools/Makefile index f038c90ba9..325c0995ee 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -123,7 +123,7 @@ define PrepareStaging $(if $(QUIET),,set -x;) \ mkdir -p "$$dir"; \ cd "$$dir"; \ - mkdir -p bin lib stamp; \ + mkdir -p bin lib stamp usr/include usr/lib; \ ); done endef -- 2.28.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
