Re: [OpenWrt-Devel] Building gdbserver
Probably I am missing something. Why just m for gdbserver? - Oliver Ertl [EMAIL PROTECTED] wrote: gdb and gdbserver builds fine here from a clean checkout. In menuconfig make sure you select: o Advanced configuration options (for developers): y o Toolchain Options o Build gdb: y o Utilities o gdbserver: m And then 'make world'. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Roberto Riggio, PhD CREATE-NET Via alla Cascata 56/C 38100 Trento (Italy) E-mail: [EMAIL PROTECTED] HomePage: http://disi.unitn.it/~riggio/ Tel: +39.0461.314.960 Fax: +39.0461.314.972 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] trouble compiling latest trunk
Yes, but that hasn't caused me issues in the past. I'll give it a try without to see if it changes anything. On Wed, 2008-04-30 at 14:37 +0200, Oliver Ertl wrote: I'm suddenly having difficulties compiling the latest trunk, and it seems to fail on random packages. It always fails with an error like this, but it seems to be on a different package everytime. Do you use parallel-building? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] trouble compiling latest trunk
I doubt this is related to the problem I was seeing, but 2.6.25 is having kernel compile issues on IXP4XX with the latest updates net/ipv4/netfilter/ipt_time.c: In function 'checkentry': net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_PRE_ROUTING' undeclared (first use in this function) net/ipv4/netfilter/ipt_time.c:97: error: (Each undeclared identifier is reported only once net/ipv4/netfilter/ipt_time.c:97: error: for each function it appears in.) net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_LOCAL_IN' undeclared (first use in this function) net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_FORWARD' undeclared (first use in this function) net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_LOCAL_OUT' undeclared (first use in this function) make[8]: *** [net/ipv4/netfilter/ipt_time.o] Error 1 make[7]: *** [net/ipv4/netfilter] Error 2 make[6]: *** [net/ipv4] Error 2 make[5]: *** [net] Error 2 make[5]: Leaving directory `/opt/openwrt/k1/build_dir/linux-ixp4xx_generic/linux-2.6.25' make[4]: *** [/opt/openwrt/k1/build_dir/linux-ixp4xx_generic/linux-2.6.25/.modules] Error 2 make[4]: Leaving directory `/opt/openwrt/k1/target/linux/ixp4xx' make[3]: *** [compile] Error 2 make[3]: Leaving directory `/opt/openwrt/k1/target/linux' make[2]: *** [target/linux/compile] Error 2 make[2]: Leaving directory `/opt/openwrt/k1' make[1]: *** [/opt/openwrt/k1/staging_dir/armeb/stamp/.target_compile] Error 2 make[1]: Leaving directory `/opt/openwrt/k1' make: *** [world] Error 2 On Wed, 2008-04-30 at 08:41 -0400, Mark Kelly wrote: Yes, but that hasn't caused me issues in the past. I'll give it a try without to see if it changes anything. On Wed, 2008-04-30 at 14:37 +0200, Oliver Ertl wrote: I'm suddenly having difficulties compiling the latest trunk, and it seems to fail on random packages. It always fails with an error like this, but it seems to be on a different package everytime. Do you use parallel-building? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] I'm integrating a more recent madwifi : any pointers?
I want to have trunk OpenWrt pick up this fix in madwifi : http://madwifi.org/changeset/3505 I've been through this exercise once before (figuring out which of the patches applied to madwifi are now included in the upstream, which are no longer needed, etc). However, I'm sure that others here know a lot more about this than I do. So I'm looking for any hints, advice, etc. For example, should I just pick whatever happens to be on the madwifi trunk today ? Or is there a golden version between 3505 and the current revision that would be better ? Is the current OpenWrt trunk known to be unstable ? Would I be better using an older revision ? Is the current code known to be stable on iXP425 ? Any help most welcome. Thanks. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Any ideas on how to work around madwifi bug #705 ?
David Boreham wrote: It turns out that trying this code is quite a bit of work (Openwrt trunk is using r3314 and the madwifi patches don't apply to r3505 or later). Last time I went through the patch set fixing it up it took a day or so. Any chance you've already made a compatible patch set ? btw, the fix I'm trying to use is in the trunk, rather than the DFS branch version you pointed me at earlier. This one : http://madwifi.org/changeset/3505 Well, what I actually meant was: try to backport this one to the OpenWrt version of MadWiFi - that shouldn't be too hard to do - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] trouble compiling latest trunk
Yes, but that hasn't caused me issues in the past. I'll give it a try without to see if it changes anything. Yes, parallel-building and ccache support is broken. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] trouble compiling latest trunk
On Wed, 30 Apr 2008, Mark Kelly wrote: I doubt this is related to the problem I was seeing, but 2.6.25 is having kernel compile issues on IXP4XX with the latest updates net/ipv4/netfilter/ipt_time.c: In function 'checkentry': net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_PRE_ROUTING' undeclared (first use in this function) net/ipv4/netfilter/ipt_time.c:97: error: (Each undeclared identifier is reported only once net/ipv4/netfilter/ipt_time.c:97: error: for each function it appears in.) net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_LOCAL_IN' undeclared (first use in this function) net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_FORWARD' undeclared (first use in this function) net/ipv4/netfilter/ipt_time.c:97: error: 'NF_IP_LOCAL_OUT' undeclared (first use in this function) make[8]: *** [net/ipv4/netfilter/ipt_time.o] Error 1 It's a problem with the patches not keeping up with 2.6.25. I have a commit poised to go in that will fix this for almost all of the netfilter modules on 2.6.25 (not IMQ, which is more complex). Just hold on a little while... and then of course fix the breakage in all the packages! -- Peter Denison ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Berekely DB porting
Zintis wrote: I'm trying to port Direct Connect Text Client for Broadcom 2.4 kernel. It needs Berkeley DB. Although there is a package in repository, it doesn't work -- I'm getting error: unable to initialize mutex: Function not implemented This might imply that the package was configured in a different environment than you are running. Did you build the package yourself ? At configure time, the bdb build detects what mutex implementation is available. If it is built somewhere where it finds for example pthread mutexes, but those are not available at runtime, you will get this error. The same error also happens if you configure on a machine with linuxthreads, but run on one with ntpl (not saying that this is your problem, but I've seen this specific bdb error many times in my travels). Berkeley homepage http://www.oracle.com/technology/products/berkeley-db/faq/db_faq.html#12 says: To avoid this error, explicitly specify the mutex implementation DB should use, with the --with-mutex=MUTEX configuration flag Does anybody can give a hint what I should write there? While googling, I found (http://fs-prisms.blogspot.com/2007/08/dtn-additional-notes.html) that for DTN it is possible to use --with-mutex=ARM/gcc-assembly I'd recommend that you build the bdb package and examine the output from configure when it's run. Feel free to post it here. I wrote some of the bdb mutex implementations way back, so I'm reasonably familiar with the space. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Why oh why...
...do we have such a big mess of patches for madwifi ? I'm just sayin... every time we pick up a new madwifi revision most of the patches need to be re-done. Has anyone tried to put, for example, the stuff that disables debug code, and the multi-binary stuff back into the upstream code ? Just seems like a strange way to make software (imho) to be spinning on these patches constantly, or alternatively failing to pick up new madwifi revisions because it's too much work to sync up. Patches that are actual bug fixes, not already in the upstream are a fine thing of course. They can be dropped as they are incorporated into madwifi. I'd be happy to work on this. Anyone tried to attack this issue already ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Why oh why...
e-mail to [EMAIL PROTECTED] Mensagem Original From: David Boreham [EMAIL PROTECTED] To: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Qua, Abril 30, 2008 8:39 pm Subject: [OpenWrt-Devel] Why oh why... ...do we have such a big mess of patches for madwifi ? I'm just sayin... every time we pick up a new madwifi revision most of the patches need to be re-done. Has anyone tried to put, for example, the stuff that disables debug code, and the multi-binary stuff back into the upstream code ? Just seems like a strange way to make software (imho) to be spinning on these patches constantly, or alternatively failing to pick up new madwifi revisions because it's too much work to sync up. Patches that are actual bug fixes, not already in the upstream are a fine thing of course. They can be dropped as they are incorporated into madwifi. I'd be happy to work on this. Anyone tried to attack this issue already ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Why oh why...
Felipe Maya wrote: e-mail to [EMAIL PROTECTED] e-mail what exactly ? Or are you just saying that's the way to ask the madwifi developers if we can add our stuff to their code ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
