Your message dated Wed, 17 Sep 2014 05:25:25 +0100
with message-id <[email protected]>
and subject line re: no cross toolchain plain communicated
has caused the Debian Bug report #753769,
regarding no cross toolchain plain communicated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
753769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753769
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:binutils-cross
Version: 0.1
Severity: serious

binutils-cross is now in unstable, however there was no discussion about the
general target to provide a cross toolchain in Debian (at least not on the
debian-cross or debian-gcc ML's).  This should be done first before any cross
toolchain component enters testing/jessie.

--- End Message ---
--- Begin Message ---
This subject has, since this bug was filed, been discussed in some
detail at the bootstrap/cross sprint.  Results reported in:
https://wiki.debian.org/Sprints/2014/BootstrapSprint/Results (and
mailed to debian-devel announce):
https://lists.debian.org/debian-devel-announce/2014/08/msg00013.html )

There is also now a general wiki page at:
https://wiki.debian.org/CrossToolchains
This will be adjusted to reflect reality for jessie and beyond as it develops.

The existing cross-binutils packages are not controversial, and are
already useful with llvm (which does not need special cross-builds the
way that gcc does). They should migrate to testing. They are
compatible with both within-arch and multiarch-built cross gcc
packages so do not affect that issue.

Wookey
-- 
Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/

--- End Message ---

Reply via email to