Date: Sat, 19 Mar 2016 19:06:08 +0200 From: David Naylor <dbn@freebsd.org> To: =?utf-8?B?QmFydMWCb21pZWo=?= Rutkowski <robak@freebsd.org> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-python@freebsd.org Subject: Re: pypy 5.0.0 on i386 Message-ID: <2372635.tnL7yCe2BY@dragon.local> In-Reply-To: <9B610B51-74D5-4968-BA91-C15A2ACF9BBC@FreeBSD.org> References: <20160314194715.GN1741@kib.kiev.ua> <9B610B51-74D5-4968-BA91-C15A2ACF9BBC@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1660408.BWUqLtlcO5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Tuesday, 15 March 2016 09:43:15 Bart=C5=82omiej Rutkowski wrote: > > On 14 Mar 2016, at 19:47, Konstantin Belousov <kostikbel@gmail.com>= wrote: > >=20 > > Hello, > > is pypy supposed to build on i386 ? I get the following error on t= he > > attempt to build pypy in i386 current jail on current amd64 box. > >=20 > > uname -a > > FreeBSD sandy32 11.0-CURRENT FreeBSD 11.0-CURRENT #919 > > r296579+bdd6db3(sysv_sem)-dirty: Thu Mar 10 12:43:41 EET 2016 =20= > > root@pooma.home:/usr/home/kostik/work/build/bsd/DEV/obj-amd64/usr/h= ome/ko > > stik/work/build/bsd/DEV/src/sys/X i386 > >=20 > > The immediate cause of the error is that vmprof_config.h is populat= ed with > > the snippet that uses mc_rip mcontext member to get instruction cou= nter > > value (seemingly). This is a valid attempt on amd64, which has %ri= p, > > but i386 has %eip for instruction counter and mcontext member is ca= lled > > mc_eip. > >=20 > > My vmprof_config.h content, I am not sure if the file is generated:= > > #define HAVE_SYS_UCONTEXT_H > > #if defined(__FreeBSD__) || defined(__APPLE__) > > #define PC_FROM_UCONTEXT uc_mcontext.mc_rip > > #else > > #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_RIP] > > #endif > >=20 > > Script of the build is attached. > >=20 > > Thanks for the advise. > > <1.log> >=20 > To be perfectly honest - I dont know, I havent done the update to 5.0= . > However, since previous versions did, I see no reason why this wouldn= t, and > I'd expect that update provided by a committer to be well tested on a= ll > supported platforms. I will make my test run, but it will take some t= ime. Hi, Apologies, it was my fault for not properly testing the PyPy update bef= ore=20 pushing it. I incorrectly assumed there wouldn't be any issues between= i386=20 and amd64. I'll ensure to run both poudriere builds before committing.= =20 This has been fixed in r411414 and reported upstream with bug #2262. =20= @kib: thank you for the report, your explanation around eip vs rip was = most=20 instrumental in finding a solution. =20 P.S. It appears that the PyPy team will be issuing a bug fix quite soon= , if=20 anyone would like to submit fixes for some unit tests ;-). =20 Regards, --nextPart1660408.BWUqLtlcO5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAABCgBmBQJW7YcAXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5NDhFQzUxMUEyN0YwMzAyRTc5OUI1M0FB RDYzRkE4REQ2QjJEQTU1AAoJEK1j+o3WstpVcTYP/0LsJKfFIjR9wtxnHNI1ryDK UyiEHefSLOcsq/nOdjEdJszct8ETXs37VnCGHuzlV2AdC/6bcJAdpaWFrnQjPtnr xB18L6Z+fRngIJQPu1KXOCLB1h9YOT2Rxa7LdwRMd7Vr77cFHM+Jp4FPdcaEqb6u 22HyS/anM7y4FtpGD46jl76m90sQrOk/BCtgT69WBf2JgKJtFcMxk6vRlU3bYwrK lnFC7cA7u8+5zbuyhKoCClI0fnuGYZxQw+2ubw56PPky8rcjWYeqOc/nrDzTOT18 IprPoc8YmRJssnwG0nOnPuIzDZQjs6SSITnYHqFAAavXqwL/bnP1XopkpBbRjqyh kWWtLHQDM9agzbu5xEfERD1R7p2SGGWMEDCcJLbyZKuwcbK/lbXL58di9RdC+Vmi 5Q3puNxz2bJPKamjMpab4g4B9g4dDh7u2zjUsTFhicV+2OsD5XE83d6hJaYnhBAt +gCWQLfUu25ZSl5t31gpjMLcOKIEyFxusA1lWUkF1iBOKdE7VT6ge+eR7ZRQGjuI oy1t6/+pv6C1SWZAZ+x+ZN2kd5PtHzlE303KOxMgTEcvC+p8OZFcx8cIxnpkHq9f dU+0k9c2dNybHX6vVs54yhRsICjzTL1gFZjXywZOwsdxUxrIXJ7HAZqqF3dn8+Wk PL6bOK0lfI7ericcHvYo =I92g -----END PGP SIGNATURE----- --nextPart1660408.BWUqLtlcO5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2372635.tnL7yCe2BY>