Hi,
> I am the Debian package maintainer of BasiliskII. Please have a look =
at
> the following which keeps the package from getting included in the =
next
> stable release of Debian:
> http://buildd.debian.org/fetch.php?&pkg=3Dbasilisk2&ver=3D0.9.20050327-=20=
> 2&arch=3Dsparc&stamp=3D1111990891&file=3Dlog&as=3Draw
I still don't know why some configure tests fail on Sparc, but I could =20=
build a version on SourceFoge.net compile farm, even without changes. =20=
Oh, I had an idea but I don't remember whether that was for Linux or =20
Solaris (I can't check as SF is currently not working for me). =20
Actually, vm_alloc tests could fail depending on where the LFS defines =20=
(#define _FILE_OFFSET_BITS 64 et al.) are placed.
Does moving AC_SYS_LARGEFILE just below the first round of programs =20
checks (at least AC_PROG_CC) help?
BTW, please don't use SDL on X11 native platforms as you would not have =20=
copy-paste of text through the X11 clipboard. The drawback of not using =20=
SDL is not using their large set of output drivers. I could write a =20
hack to grab one of the SDL X11 displays but I have not tried yet, I =20
don't know if SDL is MT safe for events handling, though it's =20
documented to be so in the sources.
> Among other things you can subscribe to new releases of the package =
and
> bugreports filed against it.
Thanks, is there any of the Debian build host publicly accessible?
Bye,
Gwenol=E9.=
|
