On 2019-01-02 8:58 p.m., Daniel F. Dickinson wrote:
> On 2019-01-02 3:06 p.m., Daniel F. Dickinson wrote:
>> Hi,
>>
>> With the SDK I'm getting errors with LTO -- at least for json-c LD is
>> trying to load the *target's* LTO plugin instead of host.
>>
>> 7.4.0_musl_eabi/bin/../libexec/gcc/arm-open
On ath79 and UBNT Bullet M XW (ar9342) I was experiencing weird issues during
network setup[1] which I was able to reproduce easily with following commands:
uci set network.lan.ipaddr='192.168.1.20'
uci commit network
ifup lan
Which resulted after some time in:
...
WARNING: CPU: 0 PID: 0 at
On 2019-01-02 3:06 p.m., Daniel F. Dickinson wrote:
> Hi,
>
> With the SDK I'm getting errors with LTO -- at least for json-c LD is
> trying to load the *target's* LTO plugin instead of host.
>
> 7.4.0_musl_eabi/bin/../libexec/gcc/arm-openwrt-linux-muslgnueabi/7.4.0/liblto_plugin.so:
> error loadin
OpenWrt presently prints the following the first time it boots:
=== WARNING! =
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--
On 2019-01-02 3:06 p.m., Daniel F. Dickinson wrote:
> Hi,
>
> With the SDK I'm getting errors with LTO -- at least for json-c LD is
> trying to load the *target's* LTO plugin instead of host.
>
For reference the error in the previous maili is *in* the SDK. Same
package being compiled for inclusion
Hi,
With the SDK I'm getting errors with LTO -- at least for json-c LD is
trying to load the *target's* LTO plugin instead of host.
Not sure where to start looking for this.
Some relevant config:
'like buildbot'
when building SDK: all packages and kernel mods and target specific
packages.
Is L
Set the LDFLAGS otherwise it will not get the target hardening flags or
any other generic flags provided in the LDFLAGS
Signed-off-by: Hauke Mehrtens
---
package/utils/bzip2/Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/utils/bzip2/Makefile b/packag
This activates the hardening features controlled over the LDFLAGS
Signed-off-by: Hauke Mehrtens
---
toolchain/musl/common.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/toolchain/musl/common.mk b/toolchain/musl/common.mk
index 234709103c..d48212f625 100644
--- a/toolchain/musl/common.mk
This includes the hardening.mk before the code gets compiled and then
also sets the LDFLAGS for the libgcc and other applications.
Signed-off-by: Hauke Mehrtens
---
include/toolchain-build.mk | 1 +
toolchain/gcc/common.mk| 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a
The kernel defines "struct sigcontext" in asm/sigcontext.h and musl libc
defines it in signal.h which collides.
Kernel 4.14 misses the definitions of struct user_sve_header so we still
have to use the aarch64-sve-linux-sigcontext.h header file which also
provides that and make sure aarch64-sve-linu
Hi,
I'll save that for when I get back to it :)
Here's how I packaged the g_cdc (ethernet+cdc-acm together)
https://github.com/karlp/openwrt/commit/40c791f5bfbbf6825087db2fc87f88a73f7fa94c
I've got a few other patches for gadgetmode, but some of it needs
a bitmore testing yet, so I've not pro
This copied to patches and the configuration for kernel 4.14 to kernel
4.19 without any manual modifications.
Signed-off-by: Hauke Mehrtens
---
target/linux/x86/64/config-4.19 | 433 +++
target/linux/x86/config-4.19 | 522 ++
target/linu
This refreshed the configuration and the patches on top of kernel 4.19.
The legacy and the genode target will not support PAE any more because
they use a CPU type which does not support PAE, the generic sub target
still supports PAE.
Signed-off-by: Hauke Mehrtens
---
target/linux/x86/64/config-
This refreshed the kernel configuration for kernel 4.14.
First this was run for the legacy target:
make kernel_oldconfig
Then for all targets including the legacy target this was run:
make kernel_oldconfig CONFIG_TARGET=subtarget
The option CONFIG_104_QUAD_8 was added to the generic
This makes it possible to use different sub target configurations for
kernel 4.19 for example.
To support kernel 4.9 and kernel 4.14 with the same configuration file
already needed some extra work.
Signed-off-by: Hauke Mehrtens
---
target/linux/x86/64/{config-default => config-4.14} | 0
ta
Hi Karl,
if you want to test it, here are the missing pieces roughly explained:
- I used kmod-usb-gadget-eth and kmod-usb-gadget-serial
I know that there is another (older?) kernel module which also provides
a network and console interface at the same time, but this must be
configured via ke
Add zone chains identifying local generated traffic; either by configuring
a loopback device or as subnet a loopback address; in the raw OUTPUT chain
as local generated traffic is passing this chain.
This allows helpers to be used for local generated traffic.
Signed-off-by: Alin Nastac
Signed-off
17 matches
Mail list logo
