[OpenWrt-Devel] External cross toolchain
Hi ML, I need your help to understand the actual status of external toolchain support. In my environment, there are a lot of developers that works on an building environment openwrt-based. Openwrt is a good choice to manage my builds and : I am happy to have chosen one year ago. The big problem that I observed is that OpenWRT doesn't support in a clean-way the external toolchains. the NATIVE_TOOLCHAIN option seems to not resolve my problems because it disables CROSS_COMPILE defines and I don't like the openwrt behaviour when this option is enabled. I want understand if are there anybody that shares my observation (or I'm not able to use native_toolchain in best way) and if a work on this topic can be appreciated by community. Kindly, give me any suggestion or opinion in order to understand what is needed to do and what I can do. thanks in advance, luigi -- Luigi Mantellini RD - Software Industrie Dial Face S.p.A. Via Canzo, 4 20068 Peschiera Borromeo (MI), Italy Tel.: +39 02 5167 2813 Fax: +39 02 5167 2459 Email: luigi.mantell...@idf-hit.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] External cross toolchain
Hi Luigi, I have a patch [1] for external toolchains support, it will allow you to select your target name (powerpc-unknow-linux-gnu), toolchain commands prefix, toolchain binaries libraries path (for toolchains installed in unusual locations and needing custom PATH LD_LIBRARY_PATH). Let me know if it works for you :) 1. http://nico-and-co.net/void/patches/openwrt-r14204-external_toolchain.patch -- Nico Luigi 'Comio' Mantellini wrote: Hi ML, I need your help to understand the actual status of external toolchain support. In my environment, there are a lot of developers that works on an building environment openwrt-based. Openwrt is a good choice to manage my builds and : I am happy to have chosen one year ago. The big problem that I observed is that OpenWRT doesn't support in a clean-way the external toolchains. the NATIVE_TOOLCHAIN option seems to not resolve my problems because it disables CROSS_COMPILE defines and I don't like the openwrt behaviour when this option is enabled. I want understand if are there anybody that shares my observation (or I'm not able to use native_toolchain in best way) and if a work on this topic can be appreciated by community. Kindly, give me any suggestion or opinion in order to understand what is needed to do and what I can do. thanks in advance, luigi ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] preliminary 2.6.29 patches
I have converted some 2.6.28 patches to apply against a linux-2.6.29-rc2 kernel. this is not a complete work as a few things still do not work but it does produce a bootable openwrt 2.6.29-rc2 system on an rb532 device. you can find these patches here: http://wifi.ozo.com/airo/openwrt/source/2.6.29/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Resume work on Asus WL500g2 (LP-PHY)
I just want to note that I resumed work on the WL500gV2, which has a b43 based LP-PHY wireless device. I cannot make any guarantees or timelines, just that it's done when it's done. I'll first look into making the serial port work. -- Greetings, Michael. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
