On Thu, Apr 11, 2013 at 03:47:19PM -0400, Jon Bernard wrote: > > 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.
BTW, it also looks like upstream has a generic implementation (gcc.h) for barriers and atomic operations. They seem to be using this only for ia64 and not on unknown architectures (probably to be on the safe side), but it might just be okay on the rest of the architectures as well. If that's the case there's probably no need to actually disable liburcu everywhere else. But you should confirm this on a per-architecture basis with your upstream :-) Regards, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
