On Mon, Jan 23, 2006 at 03:24:44PM +0100, Anselm R. Garbe wrote: > On Mon, Jan 23, 2006 at 02:03:15PM +0100, Daniel Baumann wrote: > > Paul TBBle Hampson wrote: > > > although the failed buildd runs for 9base are a problem > > > > Indeed. Anyone clue about what caused the FTBFS? I didn't look already > > into it.. > > > > http://buildd.debian.org/build.php?pkg=9base > > Those platforms who fail, are not (yet) supported or should be > treated as 386, arm, power, sun4 or x86_64 respectively. > > Each platform needs an equivalent function in a file called: > > 9base/lib9/getcallerpc-{hppa,s390,ia64}.c which returns a proper > value for following operation on 386 platform: > > #include <lib9.h> > > ulong > getcallerpc(void *x) > { > return (((ulong*)(x))[-1]); > } > > Which means returning the calling program counter as ulong. > That is afaik the only platform dependend code which is > necessary for 9base/lib9/qlock.c of 9base.
Nah, I uncommented the lock-ing stuff in qlock.c, because no program in 9base does needs locking, because no program is threaded. I'll create a snap of 9base in a minute and please let me know, if 9base compiles fine on those platforms, if you got access to any. http://wmii.de/snaps/9base-20060123.tar.gz Regards, -- Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361 _______________________________________________ [email protected] mailing list http://wmii.de/cgi-bin/mailman/listinfo/wmii
