On Thu, Apr 11, 2013 at 03:47:19PM -0400, Jon Bernard wrote:
> 
> I suspect the buildd (schroeder in this case) has a 32bit userland and thus 
> has
> a HOSTTYPE of "sparc" instead of "sparc64".  I should be a one-line patch, but
> the only available sparc test machine (smetana) is sparc64 and so I don't have
> the ability to test this.  It bothers me to make an upload simply to see if 
> the
> sparc build machine will succeed.  How would you handle this situation?

The sparc Debian port is 32-bit userland, this has nothing to do with
the buildd. The (upcoming) sparc64 port will be a separate, 64-bit
userland port. It's currently residing on debian-ports.org and buildds
are already building new uploads; it seems liburcu 0.7.6-1 built fine
there:
http://buildd.debian-ports.org/status/package.php?p=liburcu&suite=sid

Both schroeder and smetana have a 64-bit kernel, in fact I don't think
the sparc port has a 32-bit kernel at all anymore. smetana has all the
build dependencies to build liburcu on the sid chroot, if you want to
experiment.

Note that this isn't something that has recently changed, so this
doesn't explain why sparc used to work with previous liburcu versions
but stopped working. This probably has something to do with a liburcu
upstream change, you should track this down.

> > Additionally, since upstream is clearly supporting selected
> > architectures and falling back to #error for unsupported ones, your
> > package should properly mark those supported ones in the Architecture
> > field instead of relying on porters noticing and marking as Not-For-Us.
> 
> Yes, you raise an excellent point here.  I will make this change.
> 
> > It would also help reverse deps (I maintain one of them) to actually
> > know in which architectures they should limit the b-d on, since clearly
> > an unrestricted one would just result into more build failures.
> 
> Also a good point, thank you for the suggestions.

Great, thanks, looking forward to these changes.

Regards,
Faidon


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to