Le 05/11/2014 22:43, Guillaume Déflache a écrit :
Fine, but that's not the problem as I said before (see the very 1st
quoted text in this message): *installing protoc at the right location*
(that is .../build_dir/host/bin/protoc IIRC) is the problem.
I checked that with our pre-BB snapshot
Building current trunk with 3.18 kernel fired some errors like 'missed
dependancy of module XXX from library kmod_YYY.ko'. These patch fixes 3
of such issues which are critical to have a successful build.
diff --git a/include/netfilter.mk b/include/netfilter.mk
index 72c66d9..9c28a68 100644
---
On Mon, Oct 27, 2014 at 11:16:13AM +0100, Maxime Ripard wrote:
Hi Daniel,
On Sun, Oct 26, 2014 at 11:37:18PM +0100, Daniel Golle wrote:
Hi Maxime,
On Thu, Oct 09, 2014 at 05:59:27PM +0200, Maxime Ripard wrote:
On boards with large page size, the rootfs we generate might end up using
VGV7519 board have two chip at 0xb000 and 0xb4000
Which is the correct syntax?
compatible = lantiq,nor;
bank-width = 2;
reg = 0 0x0 0x80
1 0x0 0x80;
or
compatible = lantiq,nor;
bank-width = 2;
reg = 0 0x0 0x80,
1 0x0 0x80;
Does lantiq,nor support this
Your patch is broken.
Its missing the 3rd line after the 3rd chunk where you added
+$(eval $(call nf_add,IPT_NAT,CONFIG_IP_NF_TARGET_MASQUERADE,
$(P_V4)nf_nat_masquerade_ipv4, ge 3.18.0))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Your patch is broken.
Its missing the 3rd line after the 3rd chunk where you added
+$(eval $(call nf_add,IPT_NAT,CONFIG_IP_NF_TARGET_MASQUERADE,
$(P_V4)nf_nat_masquerade_ipv4, ge 3.18.0))
Yes, I see. And also I'd send it in process of reading
'SubmittingPatches' wiki (this is my first
From: Alexey N Vinogradov a.n.vinogra...@gmail.com
Building current trunk with 3.18 kernel fired some errors like 'missed
dependancy of module XXX from library kmod_YYY.ko'. These patch fixes 3
of such issues which are critical to have a successful build.
Signed-off-by: Alexey N Vinogradov
The last changes in image.mk changed build order and targets. Now
squashfs is not build 'always', and even if it is defined in the config,
it will be built after Image/Build/Initramfs. So, the last will fail
(because root.squashfs is reffered in ubinize.cfg). Note that with this
patch you still
Signed-off-by: Alexey N Vinogradov a.n.vinogra...@gmail.com
---
diff --git a/target/linux/bcm53xx/image/Makefile
b/target/linux/bcm53xx/image/Makefile
index b2fafd9..599af4e 100644
--- a/target/linux/bcm53xx/image/Makefile
+++ b/target/linux/bcm53xx/image/Makefile
@@ -9,7 +9,7 @@ include
Sometimes squashfs is necessary for other targets (say, initramfs). In
this case it may not be explicitly checked in the config, and squash fs
block size will not be explicitly defined. This patch will set this
value to 256k in such case.
Signed-off-by: Alexey N Vinogradov
10 matches
Mail list logo
