Re: pkg/51534: qemu-2.7.0 fails to build: bad register name

[Kamil Rytarowski <n54%gmx.com@localhost>]

The following reply was made to PR pkg/51534; it has been noted by GNATS.

From: Kamil Rytarowski <n54%gmx.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/51534: qemu-2.7.0 fails to build: bad register name
Date: Fri, 7 Oct 2016 21:16:10 +0200

 This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
 --9HaNvqsDCpRp2C6SrV1G1NUBfAxcvmicu
 Content-Type: multipart/mixed; boundary="PgreKNUoQbaTDxp6DjssaDxvab7SLStXf"
 From: Kamil Rytarowski <n54%gmx.com@localhost>
 To: gnats-bugs%NetBSD.org@localhost
 Message-ID: <6129fb39-7ff3-aaee-3d60-0336ed393846%gmx.com@localhost>
 Subject: Re: pkg/51534: qemu-2.7.0 fails to build: bad register name
 References: <pr-pkg-51534%gnats.netbsd.org@localhost>
  <20161006191814.E3DE07A2A9%mollari.NetBSD.org@localhost>
  <20161007120501.5972D7A2A9%mollari.NetBSD.org@localhost>
 In-Reply-To: <20161007120501.5972D7A2A9%mollari.NetBSD.org@localhost>
 
 --PgreKNUoQbaTDxp6DjssaDxvab7SLStXf
 Content-Type: text/plain; charset=windows-1252
 Content-Transfer-Encoding: quoted-printable
 
 
 
 On 07.10.2016 14:05, Jonathan Perkin wrote:
 > The following reply was made to PR pkg/51534; it has been noted by GNAT=
 S.
 >=20
 > From: Jonathan Perkin <jperkin%joyent.com@localhost>
 > To: Joerg Sonnenberger <joerg%bec.de@localhost>
 > Cc: gnats-bugs%NetBSD.org@localhost, pkg-manager%netbsd.org@localhost, gnats-admin@netbsd.o=
 rg,
 > 	pkgsrc-bugs%netbsd.org@localhost, kuehro%posteo.de@localhost
 > Subject: Re: pkg/51534: qemu-2.7.0 fails to build: bad register name
 > Date: Fri, 7 Oct 2016 13:02:42 +0100
 >=20
 >  * On 2016-10-07 at 12:51 BST, Joerg Sonnenberger wrote:
 > =20
 >  > On Fri, Oct 07, 2016 at 09:30:01AM +0000, Kamil Rytarowski wrote:
 >  > >  Solution:
 >  > >  http://netbsd.org/~kamil/patch-00011-COMPILER_WRAPPERS_APPEND_ABI=
 =2Etxt
 >  > > =20
 >  > >  Another one for cwrappers:
 >  > >  http://netbsd.org/~kamil/patch-00011-PREPEND-2.txt
 >  > > =20
 >  > >  I prefer the first one.
 >  >=20
 >  > As I said before, the first one doesn't make sense. Mixing 32bit and=
 
 >  > 64bit ABI is quite common in packages that want to specify an explic=
 it
 >  > ABI in first place.
 > =20
 >  It would also permanently break platforms where the target ABI is
 >  different from the compiler default.
 > =20
 >  --=20
 >  Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com
 > =20
 >=20
 
 1. qemu hardcodes cpu flags in its Makefiles
 2. changing from append to prepend is no-operation for qemu
 3. changing from append to prepend might create new hard to debug issues
 (like ABI mismatch) in fragile makefiles as the last -mABI wins and it
 won't be corrected
 
 This is why I prefer to let some software to have specified/injected
 ${_COMPILER_ABI_FLAG.${ABI}} where needed. And my '-1" patch must be
 extended to pass ${_COMPILER_ABI_FLAG.${ABI}} accordingly. Changing
 things to prepend just hides the issue. For now just qemu is affected
 and I wouldn't reinvent new way to inject -mABI for every package for
 singular exceptions.
 
 
 --PgreKNUoQbaTDxp6DjssaDxvab7SLStXf--
 
 --9HaNvqsDCpRp2C6SrV1G1NUBfAxcvmicu
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2
 
 iQIcBAEBCAAGBQJX9/SDAAoJEEuzCOmwLnZsptAQAI11KonQ93QUwBOyFhRQwjNS
 LeZElV/FBSLMF+juAPevG7fAoBkVBGuJe1FgAif+2bVpVahVo/0SftLi5bUi2q/f
 1/x8Fw+Bi2muUOjDf9RDnI7yDSHzrtRinf7oCWBsGYJqSg0tJU235I63j7hc/Au7
 MxnlNwYZ1MBKnq7laoL7y/2wP2gYm68YMV6klBtyT5ha6HyOiE9xdgCKrvX23nSf
 Q/765yoGY4uzouHRb+dyQOjhU3Qm4ugtcWXO1t/sEnx5aObY5rB9QOi37qea/0Hz
 BoRbtpjWdtwpylFuz8cO6Jr8WZfPskBU7fCcuCgdxHevbhS5nfVm07nw+ouk2WDo
 bZ5XECkkDhlp2r0Yftk32hqB28y/pVLGUxyzI/rQ72lm3FrFydIm0vtWXtILK/6p
 W2dJ3pcRGvB7u1+YjfvmlpFtzug91zHQGHZ5z+dz8PKbImVglx3/zs45V/+JbDm9
 M5mu5Msm9TUxlA1LidM3+uCPHyjHyXMRWxbAE1XOVtzg5wy/WRRsBZIyR2ZX0tVV
 DRelmVNb+tKyMfoimlRo0vXMFRSrz2V+PiRczXU3Cuvv7GiiqVhaOCxGWCN2GhPq
 ztRUGUXq+rQkIWPSlO0k6yyT8vTNVZbDc0x0qO6f+9oRS4NdaADIoNdgq9pCmgo+
 kb3xtuqhy+QBUp90cP5+
 =++VV
 -----END PGP SIGNATURE-----
 
 --9HaNvqsDCpRp2C6SrV1G1NUBfAxcvmicu--