[OpenWrt-Devel] [PATCH v2] target/toolchain/Config.in: Clarify packaging of toolchain.

2014-09-30 Thread Robert P. J. Day
Change the "help" info to emphasize that this option refers specifically to packaging the toolchain that would be built anyway. Signed-off-by: Robert P. J. Day --- whoops, forgot to sign the last post. diff --git a/target/toolchain/Config.in b/target/toolchain/Config.in index eda2300..5a6ec

[OpenWrt-Devel] [PATCH] target/toolchain/Config.in: Clarify packaging of toolchain.

2014-09-30 Thread Robert P. J. Day
Change the "help" info to emphasize that this option refers specifically to packaging the toolchain that would be built anyway. --- hoping i'm not misreading this, but it seems clear that as the toolchain must be constructed anyway, this option refers only to packaging it as a tarball. diff -

[OpenWrt-Devel] docs/ directory should be removed, or README updated

2014-09-30 Thread Robert P. J. Day
as i recall, the docs/ directory was described as "horribly updated", but it is *still* referred to in the top-level README: "The OpenWrt system is documented in docs/. You will need a LaTeX distribution and the tex4ht package to build the documentation. Type "make -C docs/" to build it." eit

[OpenWrt-Devel] why does building an image builder depend on !TARGET_ROOTFS_INITRAMFS?

2014-09-30 Thread Robert P. J. Day
just noticed target/imagebuilder/Config.in: config IB bool "Build the OpenWrt Image Builder" depends on !TARGET_ROOTFS_INITRAMFS depends on !PROFILE_KCONFIG depends on !EXTERNAL_TOOLCHAIN why should building an image builder depend on !TARGET_ROOTFS_INITRAMFS? a

[OpenWrt-Devel] should remaining references to LLVM be "nuked"?

2014-09-30 Thread Robert P. J. Day
(i believe i mentioned this before) back in apr of 2013 in commit 9241c57193bb8af2c1f4944ee21249b927cfecff, llvm was described as broken for two and half years so it was "nuked", but the occasional reference to it lives on in the source tree: $ grep -r llvm * toolchain/llvm/Makefile:PKG_NAME:=l

[OpenWrt-Devel] numerous questions/patches coming in the near future

2014-09-30 Thread Robert P. J. Day
a friendly warning; i just started on an official, openwrt-based project so i will be asking numerous questions, making numerous observations and (hopefully) submitting patches to follow up on my questions and observations. don't say you weren't warned ... rday --

[OpenWrt-Devel] Trouble modifying cyrus-sasl to optionally build GSSAPI support

2014-09-30 Thread W. Michael Petullo
I am trying to modify OpenWrt's cyrus-sasl package to optionally build with GSSAPI support. I first added krb5-libs to the package as an optional dependency. Despite doing this, cyrus-sasl continued to build without GSSAPI support; I found the following in the package's config.log: configure:14957

[OpenWrt-Devel] [PATCHv2] Add support for DHT11 driver

2014-09-30 Thread harald
The DHT11 is a temperature and humidity sensor supported by linux since 3.14. This patch is tested on recent mxs with kernel 3.14.18. Signed-off-by: Harald Geyer --- Changes since last version: Add dependency on devicetree package/kernel/linux/modules/other.mk | 20

Re: [OpenWrt-Devel] Postfix on OpenWRT

2014-09-30 Thread Grzegorz Sójka
On 09/29/14 00:04, W. Michael Petullo wrote: Wow! I'm happy that someone new joined the party. Toes it mean that binary packages for Barrier Breaker are going to be available? I'm asking because during the compilation I get the following error: /mnt/trash/barrier_breaker-14.07-rc3/OpenWrt-SDK-ar

Re: [OpenWrt-Devel] [PATCH] fix the build dependencies for uhttpd and ustream-ssl

2014-09-30 Thread Bas Mevissen
On 09/30/2014 03:22 PM, Felix Fietkau wrote: > I'll repeat the point for clarity: There is no inclusion of unused > libraries going on here - at least not in the image or package repositories. > > uhttpd always needs the header of ustream-ssl, but it does not link > against the library directly

Re: [OpenWrt-Devel] b53: BCM5325 VLAN VID > 15 possible?

2014-09-30 Thread Weedy
On 29 Sep 2014 05:19, "Jonas Gorski" wrote: > > Hi, > > On Mon, Sep 29, 2014 at 10:43 AM, Ilya Lipnitskiy > wrote: > > Greetings! > > > > I have been trying to configure a NETGEAR WNDR3400 device to use VLAN ID 201 > > on its WAN port to be able to talk to a Calix FTTH ONT. Studying the > > probl

Re: [OpenWrt-Devel] [PATCH] fix the build dependencies for uhttpd and ustream-ssl

2014-09-30 Thread Felix Fietkau
On 2014-09-30 09:59, Bas Mevissen wrote: > On 09/29/2014 04:32 PM, thomas.lan...@lantiq.com wrote: >> Hello Bas, >> > > Hi Thomas, > > > (...) >> >> My goal was to have the build dependencies reduced for the case no ssl is >> enabled. >> And that was fixed now with the help of Felix. >> It

Re: [OpenWrt-Devel] [PATCH] fix the build dependencies for uhttpd and ustream-ssl

2014-09-30 Thread Bas Mevissen
On 09/29/2014 04:32 PM, thomas.lan...@lantiq.com wrote: > Hello Bas, > Hi Thomas, (...) > > My goal was to have the build dependencies reduced for the case no ssl is > enabled. > And that was fixed now with the help of Felix. > It was never an issue that the libraries were included to the i

[OpenWrt-Devel] [PATCH] ar71xx: fix reset button gpio for OM2P/OM2P-HS

2014-09-30 Thread Sven Eckelmann
From: Oren Poleg A typo in the definition for the OM2P reset button disabled its functionality in OpenWrt. The actual button for these two devices is "1" and not "11". Signed-off-by: Oren Poleg [s...@open-mesh.org: added a commit subject+message] Signed-off-by: Sven Eckelmann --- target/linux

[OpenWrt-Devel] qemu/malta build error: "consider recompiling with interlinking enabled"

2014-09-30 Thread Robert P. J. Day
i'm just not having a lot of luck here ... current build error for qemu/malta image fails with: make[8]: Entering directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/lib/odbc/c_src' make -f mipsel-openwrt-linux-gnu/Makefile TYPE=opt make[9]: E