Re: Report 3 — Multiarc h cross-toolchains
Thibaut Girka <[email protected]>
| Newsgroups | gmane.linux.debian.devel.embedded |
|---|---|
| Message-ID | <20120730211444.GA29227@debian-thib> |
On Mon, Jul 30, 2012 at 03:59:47PM -0500, Jonathan Nieder wrote: > Thibaut Girka wrote: > > > * However, it would involve some additional scripting/manual intervention > > to prevent cross-built libs to be uploaded. This can be fixed before the end > > of the GSoC, and it hopefully will be. > > Is that even desirable? If the cross-building rules are correct, a > cross-built library is just as functional as, say, a library built > "natively" on a qemu-emulated target machine with > DEB_BUILD_OPTIONS=nocheck, right? Yes, it should be. But we're talking about things like libgcc, being cross-built as part of the cross-compiler build process. Such binary packages shouldn't be built, or at least not by default: they should already be in the archive, and the cross-compiler upload would be rejected. > I'd think that it would be enough to make sure the policies are clear > for human beings and people running autobuilders. > > Thanks, > Jonathan
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQFvlEAAoJEOY0VNOn/l3WBl0P/i3O944WM9zoO7Oka8dSs3CX RhaTRx8aHDhFGySuPQCahS6Y9uOJF6RWXcbELbp5tbFsN5a8lbXLGlqjQahZ4EjD lBk9b41k1OciXI8I+unPSXh8XHKfQCntncpKxSeRFHynnAuvXDr7hzy9g7o6ZbFZ Z+YiGUncXhSwxkhBUILIsoWc9KVdGUma49S5V/0iosX8uGgbPkc/t2G7pFpRtYDn hwjZjE6Vp4ubVb3Hh15j7SWWO71SwiErzHBHz1Cj+GqgzNi1QierVwIKx6hH7UA3 rCIlybgjiFzFRjvLzl/k0BwBsj8DLMxMfFm6FWidwYFx/zkWeJoaXz2VivE6mvWM nWQG94jiHYqPs8nRHMeIHhpV5o9wYhydabzQ6WAGwKDI7B1VFrFZt5M46eaa+AvV Xt/eSjJT8QQKPaeHmsoBpgyIDb0rnIuEDgMZvR0ONDIlW8woC+y3H4hB165Ai+S/ GJ9Oy3rxDNTdAwOLCOP5IJNezkVGdNGtfwS8iZ95VtNqht70LFN9CakMrINiA6gx zIvJ9w9+ULWLSCFJBBJjaK95pSKiea+22mPhA0CDVPaD+zeRWszVYzTvodw9jOeB RDvNi/AWj2FgPfTz5RfS0KXBL3i53hSoeA2JtwF0pDZJ/EzCcGapAc1U47T2k5rF nfoY87bXLSkhgjjxvp/u =WahA -----END PGP SIGNATURE-----