I think we should probably have a table rather like that in mk-sbuild
(perhaps reduced) of which architecture combinations can use native
chroots, and generate native-building chroots in those cases rather than
cross-building ones; so in the i386-on-amd64 case we would set
self.native_arch to "i386
There was a problem with the sources.list generation in the chroot, the
linked branch fixes this.
However there is still the problem that the chroot expects to have a
"g++-%s" % target_tuple
package to do the cross build. So your example will stil fail.
I would like to get feedback from Colin
** Branch linked: lp:~mvo/click/lp1319153-chroot-create
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319153
Title:
Failes to create x86 chroot
To manage notifications about this bug go to:
https:
I can confirm this issue.
** Changed in: click (Ubuntu)
Importance: Undecided => High
** Changed in: click (Ubuntu)
Status: New => Triaged
** Changed in: click (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
You received this bug notification because you are a member of
