Daniel Baumann writes:
> ah, ok.. so it will not be built on kfreebsd-amd64 then i presume.
Right, you'd need any-amd64 for that.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--
To UNSUBSCRIB
Daniel Baumann writes:
> that's known, upstream for the time being only supports this on amd64
> only, and it's unlikely to be ported to other architectures anytime soon.
I suspected as much.
> i used 'Architecture: linux-amd64' as i do in another package, however,
> ftp-master rejected that, i
On 07/31/2012 07:52 PM, Aaron M. Ucko wrote:
> Thanks for clarifying. For historical reasons, Debian generally calls
> for tagging Linux architectures explicitly only when wildcarding; please
> try "Architecture: amd64", without the "linux-".
ah, ok.. so it will not be built on kfreebsd-amd64 the
severity 683416 wishlist
retitle 683416 add support for other arches than amd64 or exclude it
tag 683416 upstream
thanks
On 07/31/2012 07:27 PM, Aaron M. Ucko wrote:
> It looks like crtools only supports amd64, at least so far: builds on other
> architectures fail when trying to compile syscall-co
Source: crtools
Version: 0.1-1
Severity: serious
Justification: fails to build from source
It looks like crtools only supports amd64, at least so far: builds on other
architectures fail when trying to compile syscall-common-x86-64.S, which
has no equivalent for other platforms AFAICT. That's fair
5 matches
Mail list logo
