Re: [OpenWrt-Devel] CFE help for bricked WRT54GS v2.
On Sun, 2012-12-16 at 19:34 +, Ch'Gans wrote: Hi there, We have a bricked WRT54GS v2 here, and are trying to bring it back to life, with no success so far. Are there any CFE/images guru around? I've connected the router and the host computer together and setup a tftp server. from CFE i can load and flash a file. The problem is that none of my attempts succeed. I tried things like: flash -noheader 192.168.1.2:openwrt-wrt54gs-squashfs.bin flash0.os i tried combinations: - with or without -header - squashfs.bin vs .trx - flash0.os vs flash0.trx - flash0 vs flash1 but none of them works. the best case gave ne a checksum error. Does anyone know the magic command do reflash the router via CFE and TFTP? Thanks in advance. Chris ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel On Linksys E3000; I use this: At CFE Prompt: upgrade code.bin On Computer:tftp -4 -m octet 192.168.1.1 -c put openwrt-e3000_v1-squashfs.bin Typing help or help command at the CFE prompt might give you additional clues as to what is supported. Nathan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] new package ndpi-netfilter
Hi, On 12/17/12 05:41, Vince Huang wrote: I have compiled it without error.But how can I test if it is working properly?Give some commands,please. Under https://dev.openwrt.org/ticket/12598 you will find a much cleaner patch and some hints. the package were renamed to iptables-mod-ndpi and kmod-ipmt-ndpi. -- iptables -m ndpi --help -- and for example iptables -I OUTPUT -m ndpi --http -j REJECT to block outgoing http traffic. It could then also be interesting to use use for traffic shaping rules or in conjunction with collectd to have a look what kind of traffic is on your net. cheers thomas -- Original -- *From: * Thomas Heilh...@terminal-consulting.de; *Date: * Sat, Dec 8, 2012 04:51 AM *To: * OpenWrt Development Listopenwrt-devel@lists.openwrt.org; *Subject: * [OpenWrt-Devel] new package ndpi-netfilter Hi, Here is ndpi-netfilter, a GPL implementation of an iptables and netfilter module for nDPI integration into the Linux kernel. If you find it useful, please integrate it. -- # # Copyright (C) 2010 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. # include $(TOPDIR)/rules.mk PKG_NAME:=ndpi-netfilter PKG_REV:=5847 PKG_RELEASE:=2 PKG_VERSION:=1.0 PKG_SOURCE:=ndpi-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=https://svn.ntop.org/svn/ntop/trunk/nDPI PKG_SOURCE_SUBDIR:=ndpi-netfilter-$(PKG_VERSION) PKG_SOURCE_VERSION:=$(PKG_REV) PKG_SOURCE_PROTO:=svn include $(INCLUDE_DIR)/package.mk #PKG_FIXUP:=autoreconf PKG_FIXUP:=libtool define Package/ndpi-netfilter SUBMENU:=Firewall SECTION:=net CATEGORY:=Network TITLE:=ndpi successor of OpenDPI URL:=http://www.ntop.org/products/ndpi/ DEPENDS:=+iptables +iptables-mod-conntrack-extra endef define Package/ndpi-netfilter/description nDPI is a ntop-maintained superset of the popular OpenDPI library endef CONFIGURE_VARS:= \ CC=$(TARGET_CC) \ LD=$(TARGET_LD) \ LIBTOOL=$(STAGING_DIR)/host/bin/libtool CONFIGURE_ARGS := \ $(filter-out --disable-nls,$(CONFIGURE_ARGS)) \ --with-pic \ TARGET_LDFLAGS += -L$(STAGING_DIR)/usr/lib/libiconv-full/lib -L$(STAGING_DIR)/usr/lib -lc -L$(TOOLCHAIN_DIR) define Build/Prepare $(call Build/Prepare/Default) rm -rf $(PKG_BUILD_DIR)/ndpi-netfilter git clone https://github.com/ewildgoose/ndpi-netfilter $(PKG_BUILD_DIR)/ndpi-netfilter endef define Build/Compile $(MAKE) -C $(PKG_BUILD_DIR) \ DESTDIR=$(PKG_INSTALL_DIR) \ CC=$(TARGET_CC) \ CFLAGS=$(TARGET_CFLAGS) $(TARGET_CPPFLAGS) $(FPIC) -I$(STAGING_DIR)/usr/include \ LD=$(TARGET_LD) \ CROSS_COMPILE=$(TARGET_CROSS) \ LDFLAGS=$(TARGET_LDFLAGS) \ all $(MAKE) -C $(PKG_BUILD_DIR)/ndpi-netfilter \ ARCH=$(LINUX_KARCH) \ CC=$(TARGET_CC) \ LDFLAGS=$(TARGET_LDFLAGS) -L$(STAGING_DIR)/usr/lib \ LD=$(TARGET_LD) \ NDPI_PATH=$(PKG_BUILD_DIR) \ KERNEL_DIR=$(LINUX_DIR) \ $(TARGET_CONFIGURE_OPTS) \ STAGING_DIR=$(STAGING_DIR) \ CROSS_COMPILE=$(TARGET_CROSS) \ CFLAGS=$(TARGET_CFLAGS) $(TARGET_CPPFLAGS) $(FPIC) -I$(STAGING_DIR)/usr/include -I$(PKG_BUILD_DIR)/ndpi-netfilter/src -I$(PKG_BUILD_DIR)/src/include \ all endef define Package/ndpi-netfilter/install mkdir -p $(1)/usr/lib/iptables $(CP) $(PKG_BUILD_DIR)/ndpi-netfilter/ipt/libxt_ndpi.so $(1)/usr/lib/iptables endef include $(INCLUDE_DIR)/kernel.mk define KernelPackage/ipt-ndpi SUBMENU:=Netfilter Extensions TITLE:= nDPI net netfilter module DEPENDS:=+kmod-ipt-compat-xtables +libpcap +ndpi-netfilter KCONFIG:=CONFIG_NF_CONNTRACK \ CONFIG_NF_CONNTRACK_EVENTS=y FILES:= \ $(PKG_BUILD_DIR)/ndpi-netfilter/src/xt_ndpi.ko AUTOLOAD:=$(call AutoLoad,46,xt_ndpi) endef $(eval $(call BuildPackage,ndpi-netfilter)) $(eval $(call KernelPackage,ipt-ndpi)) -- cheers thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] CFE help for bricked WRT54GS v2.
2012/12/17 Nathan Hintz nlhi...@hotmail.com: On Sun, 2012-12-16 at 19:34 +, Ch'Gans wrote: Hi there, We have a bricked WRT54GS v2 here, and are trying to bring it back to life, with no success so far. Are there any CFE/images guru around? I've connected the router and the host computer together and setup a tftp server. from CFE i can load and flash a file. The problem is that none of my attempts succeed. I tried things like: flash -noheader 192.168.1.2:openwrt-wrt54gs-squashfs.bin flash0.os i tried combinations: - with or without -header - squashfs.bin vs .trx - flash0.os vs flash0.trx - flash0 vs flash1 but none of them works. the best case gave ne a checksum error. Does anyone know the magic command do reflash the router via CFE and TFTP? Thanks in advance. Chris ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel On Linksys E3000; I use this: At CFE Prompt: upgrade code.bin On Computer:tftp -4 -m octet 192.168.1.1 -c put openwrt-e3000_v1-squashfs.bin Typing help or help command at the CFE prompt might give you additional clues as to what is supported. Hi Nathan, Thanks for the info. Btw, where did u get this openwrt-e3000_v1-squashfs.bin file? Did u build it yourself? If so, which branch did u used? Are you using the patch set mentioned at http://wiki.openwrt.org/toh/linksys/e3000 ? We have a guy here that would like to install openwrt on his E3000, but without success so far. Any information would be greatly appreciated. Thanks, Chris Nathan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] new package ndpi-netfilter
Yes,I use the Makefile you posted on trac. But I can still surf webs after this : iptables -I OUTPUT -m ndpi --http -j REJECT This means it's not working properly? -- Original -- From: Thomas Heilh...@terminal-consulting.de; Date: Mon, Dec 17, 2012 05:21 PM To: openwrt-developenwrt-devel@lists.openwrt.org; Subject: Re: [OpenWrt-Devel] new package ndpi-netfilter Hi, On 12/17/12 05:41, Vince Huang wrote:I have compiled it without error.But how can I test if it is working properly?Give some commands,please. Under https://dev.openwrt.org/ticket/12598 you will find a much cleaner patch and some hints. the package were renamed to iptables-mod-ndpi and kmod-ipmt-ndpi. -- iptables -m ndpi --help -- and for example iptables -I OUTPUT -m ndpi --http -j REJECT to block outgoing http traffic. It could then also be interesting to use use for traffic shaping rules or in conjunction with collectd to have a look what kind of traffic is on your net. cheers thomas -- Original -- From: Thomas Heilh...@terminal-consulting.de; Date: Sat, Dec 8, 2012 04:51 AM To: OpenWrt Development Listopenwrt-devel@lists.openwrt.org; Subject: [OpenWrt-Devel] new package ndpi-netfilter Hi, Here is ndpi-netfilter, a GPL implementation of an iptables and netfilter module for nDPI integration into the Linux kernel. If you find it useful, please integrate it. -- # # Copyright (C) 2010 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. # include $(TOPDIR)/rules.mk PKG_NAME:=ndpi-netfilter PKG_REV:=5847 PKG_RELEASE:=2 PKG_VERSION:=1.0 PKG_SOURCE:=ndpi-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=https://svn.ntop.org/svn/ntop/trunk/nDPI PKG_SOURCE_SUBDIR:=ndpi-netfilter-$(PKG_VERSION) PKG_SOURCE_VERSION:=$(PKG_REV) PKG_SOURCE_PROTO:=svn include $(INCLUDE_DIR)/package.mk #PKG_FIXUP:=autoreconf PKG_FIXUP:=libtool define Package/ndpi-netfilter SUBMENU:=Firewall SECTION:=net CATEGORY:=Network TITLE:=ndpi successor of OpenDPI URL:=http://www.ntop.org/products/ndpi/ DEPENDS:=+iptables +iptables-mod-conntrack-extra endef define Package/ndpi-netfilter/description nDPI is a ntop-maintained superset of the popular OpenDPI library endef CONFIGURE_VARS:= \ CC=$(TARGET_CC) \ LD=$(TARGET_LD) \ LIBTOOL=$(STAGING_DIR)/host/bin/libtool CONFIGURE_ARGS := \ $(filter-out --disable-nls,$(CONFIGURE_ARGS)) \ --with-pic \ TARGET_LDFLAGS += -L$(STAGING_DIR)/usr/lib/libiconv-full/lib -L$(STAGING_DIR)/usr/lib -lc -L$(TOOLCHAIN_DIR) define Build/Prepare $(call Build/Prepare/Default) rm -rf $(PKG_BUILD_DIR)/ndpi-netfilter git clone https://github.com/ewildgoose/ndpi-netfilter $(PKG_BUILD_DIR)/ndpi-netfilter endef define Build/Compile $(MAKE) -C $(PKG_BUILD_DIR) \ DESTDIR=$(PKG_INSTALL_DIR) \ CC=$(TARGET_CC) \ CFLAGS=$(TARGET_CFLAGS) $(TARGET_CPPFLAGS) $(FPIC) -I$(STAGING_DIR)/usr/include \ LD=$(TARGET_LD) \ CROSS_COMPILE=$(TARGET_CROSS) \ LDFLAGS=$(TARGET_LDFLAGS) \ all $(MAKE) -C $(PKG_BUILD_DIR)/ndpi-netfilter \ ARCH=$(LINUX_KARCH) \ CC=$(TARGET_CC) \ LDFLAGS=$(TARGET_LDFLAGS) -L$(STAGING_DIR)/usr/lib \ LD=$(TARGET_LD) \ NDPI_PATH=$(PKG_BUILD_DIR) \ KERNEL_DIR=$(LINUX_DIR) \ $(TARGET_CONFIGURE_OPTS) \ STAGING_DIR=$(STAGING_DIR) \ CROSS_COMPILE=$(TARGET_CROSS) \ CFLAGS=$(TARGET_CFLAGS) $(TARGET_CPPFLAGS) $(FPIC) -I$(STAGING_DIR)/usr/include -I$(PKG_BUILD_DIR)/ndpi-netfilter/src -I$(PKG_BUILD_DIR)/src/include \ all endef define Package/ndpi-netfilter/install mkdir -p $(1)/usr/lib/iptables
Re: [OpenWrt-Devel] new package ndpi-netfilter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 But I can still surf webs after this : iptables -I OUTPUT -m ndpi --http -j REJECT This means it's not working properly? No this means you should use FORWARD instead of OUTPUT when browsing via the router... ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDPG7UACgkQdputYINPTPNGHQCfZ+vL+jRfUNy0r5BO484UCUwz GOoAn1Ktms6vLiycdsnJAEsiIfW5Hz+O =MBcN -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCHv2] Add support for Huawei E970
Hi, Am Do, 13.12.2012, 20:59 schrieb Florian Fainelli: Le 13/12/2012 20:45, Hauke Mehrtens a écrit : Changes from previous patch: * rebased to svn-rev. 33761 * b43 wireless now works out of box (no changes were necessary on my part) * modifications according to comments by Hauke Mehrtens on 2012-04-25 * header for factory update package now created using dd and echo, no need for binary header template file anymore I just had a closer look at the patch. I do not like the way how this is added, but if you just have 2 seconds time to call the gpio I do not know a better way. How long do you have to send the ping on the gpio after the boot? Do you have a log for me without this patch, so that I can see if there is a better position for this code? Plus, this should be made a generic gpio-watchdog driver, there is nothing specific about such a thing. I already asked for that during the first round of the review AFAIR. -- Florian thanks Florian for the hint, I almost forgot about that discussion -- yet I even already proposed a gpio_wdt module based on the MTX-1 module back then :-) (see https://lists.openwrt.org/pipermail/openwrt-devel/2011-December/013159.html) Hauke: I'll look into reworking this to use arch_initcall() etc. (I guess that would be something like what you proposed last week?) Side question: were there any changes to build_dir structure in trunk recently? Previously (in October, svn-rev. 33761) kernel sources were under build_dir/linux-brcm47xx/linux-3.3.8/ I just did an svn update (rev. 34725), and now they seem to be in build_dir/target-mipsel_uClibc-0.9.33.2/linux-brcm47xx/linux-3.6.10/ Is it supposed to be like this, or has there sth. gone wrong within my build tree? Regards, Mathias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt hang when turn wifi on
Nguyen, I apologize I just now got to look at the log. The image is showing that it was created almost 1 year ago. This system is actually still running Madwifi. Perhaps the device didn't actually upgrade with your new image. On 12/14/2012 09:06 PM, Nguyễn Hồng Quân wrote: Hello Jonathan, Here is my dmesg output before I enable wifi On Fri 14 Dec 2012 09:07:57 PM ICT, Jonathan Bither wrote: Hello Nguyen, Would you be able to provide me with a 'dmesg' prior to starting wifi? On 12/14/2012 03:46 AM, Nguyễn Hồng Quân wrote: Hello, I'm building OpenWrt for Fonera router (FON2100) (Atheros target). By default, Wifi is off. But when I turn on the Wifi, OpenWrt freezes. There is even not output to Terminal (I flash firmware via serial cable). Did I build the firmware wrong or something else? Any help? Thanks. -- Regards, Quân Y!IM: ng_hquan_vn GTalk: ng.hong.quan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenVPN with netifd
Thank you very much. I don't remember at what stage the .tgz was but I'm sure I have improved the scripts meanwhile. Since I see you're interrested, I'm going to fuddle my current files together into a new tgz. The current implementation is thought in this way: when the (virtual) interface is brought up, then try to establish the tunnel until the interface is brought down. If no real path to the OpenVPN server is available, it will try again until there is one. This way I didn't require a dependency for a real interface up to now. For multiple internet interfaces, the default route or - if set - specific multiwan rules are applied. Binding to a specific interface is still possible in the openvpn config file, but only to the real interface name. Binding it to a uci network name would require additional coding in the start script - and additionally the dependency to the bound interface being up. I'm planning on publishing my files to svn, but was away for a while and didn't find the time. Great that it is useful for you, I'm looking forward for your feedback. Cheers Joachim Am 14.12.2012 14:22, schrieb Brian J. Murrell: Nice work on netifdizing OpenVPN! I'm really looking forward to patching all of your scripts from http://pariah-angels.de/openwrt/openvpn-interface.tgz into my AA-rc1 installation I have here. Any chance you might want to publish an AA ipk for it? :-) I wonder what your thoughts are on the applicability of your existing work to a router with 1 external (i.e. Internet) interfaces (and therefore more than one external IP address). In such a case, (AFAIU, anyway) one typically chooses one of the interfaces and tells OpenVPN to bind to it. Also, being totally new to this netifd stuff, I am just trying to figure out the facilities available to proto scripts, so I could totally be missing it here, but does your proto script have a dependency on an Internet interface being up? That is, will ifup for an OpenVPN interface only succeed if a real interface, providing connectivity upstream, is already plumbed? In a message thread on the -users lists where I was trying to get an HE IPv6 tunnel up, Jow showed me where the 6in4 proto fails unless there is a route to 0.0.0.0 present using: ( proto_add_host_dependency $cfg 0.0.0.0 ) I wonder if that is applicable here. But more importantly, for 1 external interface systems, having a dependency on interface OpenVPN intends to bind to would be even more important. Looking forward to your thoughts. Cheers, b. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenVPN with netifd
On 12-12-17 11:48 AM, Joachim Schlipper wrote: I don't remember at what stage the .tgz was but I'm sure I have improved the scripts meanwhile. Since I see you're interrested, I'm going to fuddle my current files together into a new tgz. Awesome. Thanks! The current implementation is thought in this way: when the (virtual) interface is brought up, then try to establish the tunnel until the interface is brought down. If no real path to the OpenVPN server is available, it will try again until there is one. This way I didn't require a dependency for a real interface up to now. For multiple internet interfaces, the default route or - if set - specific multiwan rules Hrm. I'm not familiar with these. Do you have a pointer handy? If not I can start with Google. I'm planning on publishing my files to svn, but was away for a while and didn't find the time. T'would be good if you could given that netifd is the way now. :-) Great that it is useful for you, I'm looking forward for your feedback. Cheers and much thanks for all of the work! b. signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Update for PeerVPN package (from v23 to v32)
The peervpn package in OpenWrt is outdated. Upstream recently published version 0-032 (http://www.peervpn.net/files/peervpn-0-032.tar.gz). It should be sufficient to changePKG_VERSION:=0-023toPKG_VERSION:=0-032 - Chris ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCHv2] Add support for Huawei E970
Hi Hauke, Am Do, 13.12.2012, 20:55 schrieb Hauke Mehrtens: On 11/11/2012 09:38 PM, Mathias Adam wrote: ping... Am So, 14.10.2012, 21:13 schrieb Mathias Adam: !strcmp(getvar(status_gpio), 1)) /* gpio based detection */ return platforms[PS1208MFG]; + if (!strcmp(boardnum, 0x5347) !strcmp(boardtype, 0x048e)) /* Huawei E970 */ + return platforms[HUAWEI_E970]; + These two values boardnum and boardtype do not look very device specific, could you post the nvram of the device, I hope there are some better names in it. here's nvram dump after a factory reset (serno, il0macaddr, boardno, et0macaddr are device dependent): CFE nvram show sdram_config=0x0062 sdram_refresh=0 vlan0ports=0 1 2 3 5* et0mdcport=0 bxa2g=1 vlan1hwname=et0 ag0=2 et0phyaddr=30 serno=KQ7NAB18324. pa0maxpwr=72 pa0b0=0x125d pa0b1=0xfb6e pa0b2=0xfec1 il0macaddr=00:1E:10:10:..:.. wandevs=et0 clkfreq=240 cctl=0 sdram_ncdl=0xffd08 boardnum=0x5347 ccode=0 rssisav2g=2 boardno=020HQG7N830. rssismc2g=2 rxpo2g=0xfff8 opo=12 aa0=3 pa0itssit=62 sromrev=3 boardtype=0x048e boardflags=0x750 watchdog=3000 lan_netmask=255.255.255.0 wl0id=0x4318 rssismf2g=0 boardrev=0x11 lan_ipaddr=192.168.1.1 et0macaddr=00:1E:10:10:..:.. et1phyaddr=0x1f landevs=vlan0 wl0 build_cfe_version=256.11.01.03.102sp02 sdram_init=0x000b boot_wait=on tri2g=78 vlan1ports=4 5u vlan0hwname=et0 xtalfreq=25000 wl0gpio0=11 wl0gpio1=11 wl0gpio2=11 wl0gpio3=11 size: 785 bytes (31983 left) *** command status = 0 Regards, Mathias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] r34740 trunk blockdev_direct_IO error..
hello, trying to compile latest trunk (34740) for a tp-link wr1043nd and it stops at the below parts, any ideas please? i did make clean, make dirclean, recompiled and still the same error.. thanks! make[5]: Entering directory `/home/dani/OpenWRT/rtl8366/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/linux-3.6.10' scripts/kconfig/conf --silentoldconfig Kconfig # # configuration written to .config # make[5]: Leaving directory `/home/dani/OpenWRT/rtl8366/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/linux-3.6.10' CHK include/linux/version.h CHK include/generated/utsrelease.h CALLscripts/checksyscalls.sh stdin:1220:2: warning: #warning syscall kcmp not implemented [-Wcpp] CHK include/generated/compile.h CC arch/mips/ath79/setup.o In file included from include/linux/poll.h:12:0, from include/linux/rtc.h:123, from /home/dani/OpenWRT/rtl8366/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/linux-3.6.10/arch/mips/include/asm/time.h:17, from arch/mips/ath79/setup.c:22: include/linux/fs.h: In function 'blockdev_direct_IO': include/linux/fs.h:2665:1: error: no return statement in function returning non-void [-Werror=return-type] cc1: all warnings being treated as errors make[7]: *** [arch/mips/ath79/setup.o] Error 1 make[6]: *** [arch/mips/ath79] Error 2 make[5]: *** [arch/mips] Error 2 make[4]: *** [/home/dani/OpenWRT/rtl8366/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/linux-3.6.10/.image] Error 2 make[4]: Leaving directory `/home/dani/OpenWRT/rtl8366/trunk/target/linux/ar71xx' make[3]: *** [install] Error 2 make[3]: Leaving directory `/home/dani/OpenWRT/rtl8366/trunk/target/linux' make[2]: *** [target/linux/install] Error 2 make[2]: Leaving directory `/home/dani/OpenWRT/rtl8366/trunk' make[1]: *** [/home/dani/OpenWRT/rtl8366/trunk/staging_dir/target-mips_r2_uClibc-0.9.33.2/stamp/.target_install] Error 2 make[1]: Leaving directory `/home/dani/OpenWRT/rtl8366/trunk' make: *** [world] Error 2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] -fPIC flag for nacl
* Chris Warner inh...@gmail.com [2012-12-14 07:33:43 +0430]: In order to get cjdns to cross-compile I had to enable -fPIC for the nacl package in the makefile. I have included my patch below. I am last time i checked nacl only provided statically linked binaries and it has asm implementations for certain platforms that are not position independent so -fPIC is probably not useful ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] r34740 trunk blockdev_direct_IO error..
On 2012-12-17 10:25 PM, Daniel Petre wrote: hello, trying to compile latest trunk (34740) for a tp-link wr1043nd and it stops at the below parts, any ideas please? i did make clean, make dirclean, recompiled and still the same error.. thanks! Are you sure you ran make clean after updating to r34740? I did commit a fix for this issue in that rev. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] r34740 trunk blockdev_direct_IO error..
On Dec 17, 2012, at 11:36 PM, Felix Fietkau n...@openwrt.org wrote: On 2012-12-17 10:25 PM, Daniel Petre wrote: hello, trying to compile latest trunk (34740) for a tp-link wr1043nd and it stops at the below parts, any ideas please? i did make clean, make dirclean, recompiled and still the same error.. thanks! Are you sure you ran make clean after updating to r34740? I did commit a fix for this issue in that rev. thanks for replying, i did make clean and make dirclean but this time i resetted the menuconfig to default and selected again my options, seems okay now, it compiled without errors. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 02/16] support finding /usr/share data using pkgconfig
On Mon, Aug 13, 2012 at 10:33:41PM -0700, Andy Leiserson wrote:
Allow packages to find arch-independent data normally located in
/usr/share in the staging area using pkgconfig.
Change the default configure args to use ${prefix} and ${exec_prefix}
(with expansion deferred) rather than $(CONFIGURE_PREFIX). This allows
the pkg-config wrapper used in the host staging area
(tools/pkg-config/files/pkg-config) to fully override the location of
the package by setting only $prefix and $exec_prefix, as long as the
pkgconfig files define paths in terms of those variables.
Quoting Florian's note in response to 00/16 of the series
(sent Wed, Dec 05, 2012 at 06:41:51PM +0100):
I did not apply patch 2 because I am not exactly sure everything is
required in it.
Thanks Florian for taking the time to review the patches.
I'll try to clarify the intent of patch 02, in case it wasn't clear.
Currently the issue only affects rygel, but I do think it could affect
other packages in the future. If we just need a safe fix for the rygel
issue, I can submit a patch to do that.
The problem addressed by the patch is how to tell the rygel build to
look for .vapi files in the staging area rather than in
/usr/share/vala/vapi on the host. (This is the reason the rygel
build is failing in the buildbot.)
The vala package generates a pkgconfig file called vapigen.pc using
autoconf. The vapigen.pc.in source contains (in part):
prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
datadir=@datadir@
Without the patch, those lines are expanded to say:
prefix=/usr
exec_prefix=/usr
libdir=${exec_prefix}/lib
datadir=/usr/share
The value of libdir is an autoconf-supplied default, because the openwrt
configure args in package-defaults.mk don't specify --libdir. The value
of --datadir comes from the openwrt configure args.
With the patch, the datadir line reads:
datadir=${prefix}/share
... which will point to the correct path in the staging area when the
pkg-config wrapper used by the build overrides $prefix and $exec_prefix.
There's an obvious risk that the patch will break things. So, I
understand if it can't be applied. I'll offer a few other options:
1. Manually set the vapidir path to point to the staging area in the
rygel build. (This has simplicity and safety, if not cleanliness, in
its favor.)
2. Override datadir in the pkg-config wrapper script.
3. Remove datadir (and possibly others) from the default configure args,
with the reasoning that it should match the default. (This avoids the
risk that something breaks because it isn't shell-expanding the paths
in the configure args.)
I'll submit a patch to do #1, if there isn't feedback otherwise.
Thanks,
Andy
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
