Hauke is correct. Looking at the message headers: References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <006001ccf22e$d3f79fa0$7be6dee0$@com> <[email protected]> <006301ccf52b$f9bcf190$ed36d4b0$@com> <[email protected]> <001a01ccf769$1c1644f0$5442ced0$@com> <[email protected]> <00db01cd0022$1c589d70$5509d850$@com> <[email protected]> <008501cd07f8$d81cc3a0$88564ae0$@com> <01fd01cd0826$923293a0$b697bae0$@com> In-Reply-To: <01fd01cd0826$923293a0$b697bae0$@com>
A brand new thread should not have any of these. On 3/23/12 9:48 PM, tathagata wrote: > Hi Hauke, > Sorry, I do not understand. Could you please clarify ? > > Regards, > Tatha > > On 23.03.2012 16:53, Hauke Mehrtens wrote: >> On 03/23/2012 12:48 PM, Tathagata Das wrote: >>> Hi, >>> Attached file adds uClibc configuration specification for external >>> toolchain. Instead of having to configure specifications via make >>> menuconfig for external toolchain, one may select the package >>> libuClibc, which additionally will copy ./lib/ld-uClibc* and >>> ./lib/libuClibc*. I have used latest trunk source code (revision >>> number 31050) to create this patch. >>> >>> Regards, >>> Tathagata <[email protected]> >> Hi, >> >> could you start a new thread and not replay to an completely >> unrelated >> thread when you post a patch to the mailing list. Just replay to a >> mail >> if your mail is related to it. This message does not seam to be >> related >> to WNR3500L support. >> >> Hauke > > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
