maximilian attems
2011-Jan-31 10:50 UTC
[klibc] (fwd) Re: Bug#334917: [PATCH] Re: klibc barfs on m68k syscall interface
Hello, It be cool if belows patch could be reviewed by a m68k Maintainer. It should apply to latest klibc git, which can be found on git clone git://git.kernel.org/pub/scm/libs/klibc/klibc.git klibc is most easiest to compile against a linux-2.6 configured tree with make KLIBCKERNELSRC=`pwd`/../linux-2.6 master klibc should built fine on m68k, but is not know to work: http://bugs.debian.org/334917 thank you. -- maks ----- Forwarded message from Thorsten Glaser <tg at mirbsd.de> -----
Thorsten Glaser
2011-Jan-31 22:19 UTC
[klibc] (fwd) Re: Bug#334917: [PATCH] Re: klibc barfs on m68k syscall interface
maximilian attems dixit:>It be cool if belows patch could be reviewed by a m68k Maintainer.I?ve patched mksh to work without job signals, depending on a flag; while this is not desirable generally, it allows me to run its test suite. The patch per se is correct, but may be incomplete (i.e. I still get some failures that pass on i386, where other syscalls or functions may be involved). I?ll probably debug and submit more of that later.>- blt.l 1f >+ bcs.l 1f /* jmp short if _not_ error */I think this is the one-liner (plus repeating in vfork.S, here by jumping to the common code) fixing the issue. The rest is? well? don?t hit me? me mentally converting the code of klibc and eglibc both to i386 assembly, comparing, mixing, fixing, optimising, and converting back to m68k assembly ? stylistic flames welcome! (Yes, I mean it. I?m learning this as I go.) //mirabilos -- 22:20?<asarch> The crazy that persists in his craziness becomes a master 22:21?<asarch> And the distance between the craziness and geniality is only measured by the success 22:21?<mksh> it?s a very thin line anyway? with some, you don?t know which side they?re on