On Tue, Jul 08, 2008 at 08:27:55PM +0200, Josip Rodin wrote:
> On Tue, Jul 08, 2008 at 08:16:19PM +0200, Josip Rodin wrote:
> > On Tue, Jul 08, 2008 at 08:07:09PM +0200, Josip Rodin wrote:
> > > It looks like the pdns-recursor bug #395801 may no longer be relevant
> > > (it was in 2006).
> > > 
> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=25;bug=395801
> > > from April 2007 indicates that it builds on sparc, but that message
> > > didn't reopen that bug, which in turn got archived.
> > > 
> > > The lack of packages for other architectures was just cited to me as
> > > a reason why the security team could just recommend pdns-recursor instead
> > > of bind in the recent DSA - pity.
> > > 
> > > I'll try to get something more concrete (like actual build results on
> > > agricola etc). If we have time before the full freeze, you could also try
> > > uploading a package with the Architecture tag reset to any, and see how it
> > > goes.
> > 
> > The available machines are too slow to try the full build, but I have
> > verified that <ucontext.h> defines swapcontext() the same way on all
> > of sparc, arm, mips, which is the same way as it is on e.g. amd64.
> > It looks like it's definitely worth a shot.
> 
> Hm, looking at the glibc 2.7 source and changelogs, it looks like the
> interface is there for all of them, but the default implementation just
> returns -ENOSYS :/
> 
> But, the belated submission in #395801 does seem to be correct, because
> there does exist a sysdeps/unix/sysv/linux/sparc/sparc64/swapcontext.c
> 

Support for swapcontext has been added recently in libc6 for hppa and
sparc. You can now enable pdns-recursor on those architectures. You 
should build-depends on libc6-dev (>= 2.7-14) [hppa sparc].

-- 
  .''`.  Aurelien Jarno             | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   [email protected]         | [email protected]
   `-    people.debian.org/~aurel32 | www.aurel32.net



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to