Re: Is it feasible to cross-build compat5x binary?
--3dBJfKlFjfsS/piO
Content-Type: multipart/mixed; boundary="e9fMjeYs+GPci+mg"
Content-Disposition: inline
--e9fMjeYs+GPci+mg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Oct 23, 2005 at 04:29:35PM -0700, David O'Brien wrote:
> On Sun, Oct 23, 2005 at 06:52:30PM +0800, Xin LI wrote:
> > I think we need to update compat5x binary to fix FreeBSD-SA-05:21.opens=
sl,
> > but will the binaries built by ``make universe'' be identical with actu=
al
> > build on Alpha, Sparc64, etc? (Yes, I'm volunteering to do the work iff
> > they are identical ;-)
>=20
> We should no trust cross built libraries for this purpose at this time.
> We really don't know how identical the results will be to being natively
> built.
> =20
On -CURRENT they will be identical. I regularly do test cross-builds
and do binary compares from installworld/installkernel. The
infrastructure is there, and is activated by the CROSS_BUILD_TESTING
knob: it tries to eliminate as much difference as it can, with the
help of tools/build/cross-build, and ensuring the object directory
is the same on native and foreign architectures. Attached is the
script I use to test cross-builds. I pass it buildworld, buildkernel,
installworld, installkernel, and distribution targets, and then do
binary compares. The only known decrepancy at this time is with
file(1) data files on sparc64/non-sparc64.
Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer
--e9fMjeYs+GPci+mg--
--3dBJfKlFjfsS/piO
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
iD8DBQFDYSv1qRfpzJluFF4RAi+yAJwPQBEpWwpvQqp/6tCC0qEDrWeJxgCfTrAw
Vzqp7wlStr7+Akc3nxJJzL8=
=2Pt/
-----END PGP SIGNATURE-----
--3dBJfKlFjfsS/piO--
討論串 (同標題文章)
完整討論串 (本文為第 11 之 14 篇)：