[OpenWrt-Devel] qemu/malta build error: consider recompiling with interlinking enabled
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]: 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' mipsel-openwrt-linux-uclibc-gcc -Werror=return-type -Os -pipe -mno-branch-likely -mips32 -mtune=mips32 -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -D_THREAD_SAFE -D_REENTRANT -DPOSIX_THREADS -D_POSIX_THREAD_SAFE_FUNCTIONS -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_NETDB_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SQL_H=1 -DHAVE_SQLEXT_H=1 -DHAVE_STRUCT_SOCKADDR_IN6_SIN6_ADDR=1 -DHAVE_MEMSET=1 -DHAVE_SOCKET=1 -DHAVE_PTHREAD_H=1 -DSIZEOF_VOID_P=4 -o ../priv/bin/mipsel-openwrt-linux-gnu/odbcserver ../priv/obj/mipsel-openwrt-linux-gnu/odbcserver.o -L/home/rpjday/openwrt/qemu_malta/staging_dir/target-mipsel_mips32_uClibc-0.9.33.2/usr/lib -lodbc -L/ home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/lib/erl_interface/obj/mipsel-openwrt-linux-gnu -lpthread -lerl_interface -lei /home/rpjday/openwrt/qemu_malta/staging_dir/toolchain-mipsel_mips32_gcc-4.8-linaro_uClibc-0.9.33.2/lib/gcc/mipsel-openwrt-linux-uclibc/4.8.3/../../../../mipsel-openwrt-linux-uclibc/bin/ld: ../priv/obj/mipsel-openwrt-linux-gnu/odbcserver.o: .text+0xfb8: Direct jumps between ISA modes are not allowed; consider recompiling with interlinking enabled. /home/rpjday/openwrt/qemu_malta/staging_dir/toolchain-mipsel_mips32_gcc-4.8-linaro_uClibc-0.9.33.2/lib/gcc/mipsel-openwrt-linux-uclibc/4.8.3/../../../../mipsel-openwrt-linux-uclibc/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status mipsel-openwrt-linux-gnu/Makefile:111: recipe for target '../priv/bin/mipsel-openwrt-linux-gnu/odbcserver' failed make[9]: *** [../priv/bin/mipsel-openwrt-linux-gnu/odbcserver] Error 1 make[9]: Leaving directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/lib/odbc/c_src' /home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/make/run_make.mk:34: recipe for target 'opt' failed make[8]: *** [opt] Error 2 make[8]: Leaving directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/lib/odbc/c_src' /home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/make/otp_subdir.mk:28: recipe for target 'opt' failed make[7]: *** [opt] Error 2 make[7]: Leaving directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/lib/odbc' /home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/make/otp_subdir.mk:28: recipe for target 'opt' failed make[6]: *** [opt] Error 2 make[6]: Leaving directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/lib' Makefile:451: recipe for target 'libs' failed make[5]: *** [libs] Error 2 make[5]: Leaving directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1' Makefile:379: recipe for target 'noboot' failed make[4]: *** [noboot] Error 2 make[4]: Leaving directory '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1' Makefile:324: recipe for target '/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/.built' failed make[3]: *** [/home/rpjday/openwrt/qemu_malta/build_dir/target-mipsel_mips32_uClibc-0.9.33.2/otp_src_17.1/.built] Error 2 make[3]: Leaving directory '/home/rpjday/openwrt/qemu_malta/feeds/packages/lang/erlang' package/Makefile:174: recipe for target 'package/feeds/packages/erlang/compile' failed make[2]: *** [package/feeds/packages/erlang/compile] Error 2 make[2]: Leaving directory '/home/rpjday/openwrt/qemu_malta' package/Makefile:171: recipe for target '/home/rpjday/openwrt/qemu_malta/staging_dir/target-mipsel_mips32_uClibc-0.9.33.2/stamp/.package_compile' failed make[1]: *** [/home/rpjday/openwrt/qemu_malta/staging_dir/target-mipsel_mips32_uClibc-0.9.33.2/stamp/.package_compile] Error 2 make[1]: Leaving directory '/home/rpjday/openwrt/qemu_malta' /home/rpjday/openwrt/qemu_malta/include/toplevel.mk:171: recipe for target 'world' failed make: *** [world] Error 2 a quick google brings up a few links:
[OpenWrt-Devel] [PATCH] ar71xx: fix reset button gpio for OM2P/OM2P-HS
From: Oren Poleg o...@poleg.org 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 o...@poleg.org [s...@open-mesh.org: added a commit subject+message] Signed-off-by: Sven Eckelmann s...@open-mesh.com --- target/linux/ar71xx/files/arch/mips/ath79/mach-om2p.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-om2p.c b/target/linux/ar71xx/files/arch/mips/ath79/mach-om2p.c index 24f4527..6b0bdc3 100644 --- a/target/linux/ar71xx/files/arch/mips/ath79/mach-om2p.c +++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-om2p.c @@ -31,7 +31,7 @@ #define OM2P_GPIO_LED_YELLOW 15 #define OM2P_GPIO_LED_LAN 16 #define OM2P_GPIO_LED_WAN 17 -#define OM2P_GPIO_BTN_RESET11 +#define OM2P_GPIO_BTN_RESET1 #define OM2P_KEYS_POLL_INTERVAL20 /* msecs */ #define OM2P_KEYS_DEBOUNCE_INTERVAL(3 * OM2P_KEYS_POLL_INTERVAL) -- 2.1.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fix the build dependencies for uhttpd and ustream-ssl
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 image. Well, including unused libraries is a waste of space and might be against the wish of the image creator. Also, it can be an unwanted export of crypto software too. That problem did not go away after the US changed the rules years ago. Cheers, Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fix the build dependencies for uhttpd and ustream-ssl
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 was never an issue that the libraries were included to the image. Well, including unused libraries is a waste of space and might be against the wish of the image creator. Also, it can be an unwanted export of crypto software too. That problem did not go away after the US changed the rules years ago. 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 (it uses dlopen). - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] b53: BCM5325 VLAN VID 15 possible?
On 29 Sep 2014 05:19, Jonas Gorski j...@openwrt.org wrote:
Hi,
On Mon, Sep 29, 2014 at 10:43 AM, Ilya Lipnitskiy
ilya.lipnits...@gmail.com 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
problem, I have found that the device contains a BCM5325 switch, which
only
supports up to 16 VLAN entries. However, each entry may have a VID that
is
12 bits long, ie 0-4095.
It does not seem that the current b53 driver supports this:
From b53_common.c:
static int b53_port_set_pvid(struct switch_dev *dev, int port, int val)
{
...
if (val 15 is5325(priv))
return -EINVAL;
...
I don't think this is hardware limitation, as people seem to have
gotten it
This is why you don't buy broadcom
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fix the build dependencies for uhttpd and ustream-ssl
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 (it uses dlopen). So they (the ssl libraries) only need to be available during build, but don't end up in the image (only) due to this *build* dependency? That is fine indeed. Thanks for clarifying, Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Postfix on OpenWRT
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-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/../lib/gcc/mips-openwrt-linux-uclibc/4.8.3/../../../../mips-openwrt-linux-uclibc/bin/ld: skipping incompatible /usr/lib64/libc.so when searching for -lc collect2: error: ld returned 1 exit status Makefile:50: recipe for target 'master' failed Postfix compiles fine on my build host (Fedora 20), but actually creating I chroot-installed Fedora20 x86_64. Unfortunately during the compilation I get the following error: make: Entering directory `/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/postfix-2.10.2/src/master' ccache_cc -I/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include/ -DNO_EPOLL -DNO_SIGSETJMP -DHAS_CDB -DNO_NIS -I/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/tinycdb-0.77/ -g -O -I. -I../../include -DLINUX3 -o master master.o master_conf.o master_ent.o master_sig.o master_avail.o master_spawn.o master_service.o master_status.o master_listen.o master_vars.o master_wakeup.o master_watch.o master_flow.o master_monitor.o ../../lib/libglobal.a ../../lib/libutil.a -L/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib /OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/tinycdb-0.77/libcdb.a -lpcre -lnsl -lresolv /OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/../lib/gcc/mips-openwrt-linux-uclibc/4.8.3/../../../../mips-openwrt-linux-uclibc/bin/ld: cannot find -lpcre collect2: error: ld returned 1 exit status Any ideas?? -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCHv2] Add support for DHT11 driver
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 har...@ccbib.org --- Changes since last version: Add dependency on devicetree package/kernel/linux/modules/other.mk | 20 1 files changed, 20 insertions(+), 0 deletions(-) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index d56bb50..38e6628 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -258,6 +258,26 @@ endef $(eval $(call KernelPackage,iio-ad799x)) + +define KernelPackage/iio-dht11 + SUBMENU:=$(OTHER_MENU) + DEPENDS:=kmod-iio-core @GPIO_SUPPORT @USES_DEVICETREE + TITLE:=DHT11 (and compatible) humidity and temperature sensors + KCONFIG:= \ + CONFIG_DHT11 + FILES:=$(LINUX_DIR)/drivers/iio/humidity/dht11.ko + AUTOLOAD:=$(call AutoLoad,56,dht11) +endef + +define KernelPackage/iio-dht11/description + support for DHT11 and DHT22 digitial humidity and temperature sensors + attached at GPIO lines. You will need a custom device tree file to + specify the GPIO line to use. +endef + +$(eval $(call KernelPackage,iio-dht11)) + + define KernelPackage/lp SUBMENU:=$(OTHER_MENU) TITLE:=Parallel port and line printer support -- 1.7.2.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Trouble modifying cyrus-sasl to optionally build GSSAPI support
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: checking for gss_unwrap in -lgssapi_krb5 configure:14982: mips-openwrt-linux-uclibc-gcc -o conftest -Wall -W -Os -pipe -mno-branch-likely -mips32r2 -mtune=34kc -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -mips16 -minterlink-mips16 -fpic -I/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include -I/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/include -I/home/mike/Source/openwrt/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/usr/include -I/home/mike/Source/openwrt/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/include -I/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include/krb5 -DOBSOLETE_CRAM_ATTR=1 -I/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include -L/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib -R/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_ 34kc_uClibc-0.9.33.2/usr/lib -L/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib -L/home/mike/Source/openwrt/openwrt/staging_dir/target-mips_34kc_uClibc-0.9.33.2/lib -L/home/mike/Source/openwrt/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/usr/lib -L/home/mike/Source/openwrt/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/lib conftest.c -lgssapi_krb5 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lkrb5support 5 /home/mike/Source/openwrt/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/lib/gcc/mips-openwrt-linux-uclibc/4.8.3/../../../../mips-openwrt-linux-uclibc/bin/ld: cannot find -lcom_err collect2: error: ld returned 1 exit status libcom_err seems to be a library that is part of the libext2fs package, so I added this as an optional dependency for cyrus-sasl as well. Building libext2fs did not seem to help, though; I found the same warning in config.log again. One thing I noticed is that building libext2fs results in libcom_err being installed at: staging_dir/target-mips_34kc_uClibc-0.9.33.2/root-ar71xx/usr/lib/ but not: staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib However, manually copying the library from the former directory to the later does not seem to help. Does anyone know what might be going on? -- Mike :wq ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] why does building an image builder depend on !TARGET_ROOTFS_INITRAMFS?
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? as i read it, under Target Images, i can select a variety of target image types. so why should selecting ramdisk suddenly mean i can't create an image builder? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] docs/ directory should be removed, or README updated
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. either the docs/ directory should be removed or, at the very least, the README file should be updated to warn readers about its obsolescence. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] target/toolchain/Config.in: Clarify packaging of toolchain.
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 --git a/target/toolchain/Config.in b/target/toolchain/Config.in index eda2300..5a6ecef 100644 --- a/target/toolchain/Config.in +++ b/target/toolchain/Config.in @@ -1,6 +1,8 @@ config MAKE_TOOLCHAIN - bool Build the OpenWrt based Toolchain + bool Package the OpenWrt-based Toolchain depends on !EXTERNAL_TOOLCHAIN help - This is essentially the toolchain created by OpenWrt. - + Package the created toolchain as a tarball under the bin/ directory as + OpenWrt-Toolchain-$(BOARD)-for-$(ARCH)$(ARCH_SUFFIX)-gcc-$(GCCV)$(DIR_SUFFIX). + For example, a toolchain for the MIPS architecture might be named + OpenWrt-Toolchain-malta-for-mipsel_mips32-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2. -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] target/toolchain/Config.in: Clarify packaging of toolchain.
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 rpj...@crashcourse.ca --- whoops, forgot to sign the last post. diff --git a/target/toolchain/Config.in b/target/toolchain/Config.in index eda2300..5a6ecef 100644 --- a/target/toolchain/Config.in +++ b/target/toolchain/Config.in @@ -1,6 +1,8 @@ config MAKE_TOOLCHAIN - bool Build the OpenWrt based Toolchain + bool Package the OpenWrt-based Toolchain depends on !EXTERNAL_TOOLCHAIN help - This is essentially the toolchain created by OpenWrt. - + Package the created toolchain as a tarball under the bin/ directory as + OpenWrt-Toolchain-$(BOARD)-for-$(ARCH)$(ARCH_SUFFIX)-gcc-$(GCCV)$(DIR_SUFFIX). + For example, a toolchain for the MIPS architecture might be named + OpenWrt-Toolchain-malta-for-mipsel_mips32-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2. -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
