On Sun, Feb 12, 2023 at 08:17:04AM +, Bastian Bittorf wrote:
> On Sat, Feb 11, 2023 at 02:30:44PM -0500, Rich Felker wrote:
> > > > .hidden __hwcap
> > > > .long __hwcap-.
> > > > -1: mflr 4
> > > > - lwz 5, 0(4)
&g
On Sat, Feb 11, 2023 at 07:27:39PM +, Bastian Bittorf wrote:
> On Sat, Feb 11, 2023 at 09:01:03AM -0500, Rich Felker wrote:
> > It looks like the powerpc spe longjmp code is clobbering the value
> > argument. Try the attached patch.
>
> > diff --git a/src/setjmp/powerp
On Sat, Feb 11, 2023 at 12:51:47PM +, Bastian Bittorf wrote:
> With OpenWRT i recognized a strange behavior of ash-shell scripts.
> It happens only on target PowerPC, e.g. m68k, arm, mips, x86 are
> unaffected.
>
> The visible strange behavior in 'ash' is:
>
> $ test A -gt 5 && echo OK
> ash:
On Sat, Oct 08, 2022 at 01:53:29AM +0200, Jo-Philipp Wich wrote:
> Hi,
>
> > [...]
> > Which implementation of nslookup is this? Busybox? It would probably
> > be useful to hear thoughts on it from their side.
> assuming the OP is using standard OpenWrt nslookup, it is the "big" busybox
> nslookup
On Sat, Oct 08, 2022 at 01:04:25AM +0200, Uwe Kleine-König wrote:
> Hello,
>
> on a TP-Link RE200 v1 (platform = ramips/mt7620) I experience often:
>
> root@ares:~# nslookup www.openwrt.org
> Server: 127.0.0.1
> Address: 127.0.0.1:53
>
> Non-authoritative answer:
> www.open
