Date: Mon, 11 Apr 2022 19:57:05 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: =?utf-8?Q?Fernando_Apestegu=C3=ADa?= <fernape@freebsd.org> Cc: jbo@insane.engineer, "ports@freebsd.org" <ports@freebsd.org> Subject: Re: Build issue with i386 port Message-ID: <168EF37D-8591-4F8C-93E1-F15FDA10F311@FreeBSD.org> In-Reply-To: <CAGwOe2a=oNCK8jryHMhD11OQHnAw3C34M18aVFF8tSHubYxyGQ@mail.gmail.com> References: <HHY42GcIqbl9KVSvHSzg73YO7HcDnD_PD4r9wDzBtyH0RPJcBXGdsfdwCYDixZRJRjN3qktWgORg2apUdq9YeGycdg1lLHZcyZ6PTIXTuQY=@insane.engineer> <zfL6oy-z-MOKJcsJTWbT4bXx4TCQCLUWVzLxT3DgK6tpyDutGVNFjovLSBm78Q-sDQ0lz8tx4IyODhzrDhSPRR3wXpQJ9yk-7xlDu8wiW6w=@insane.engineer> <CAGwOe2a=oNCK8jryHMhD11OQHnAw3C34M18aVFF8tSHubYxyGQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_BDE2D2B4-A84C-4271-85C2-60B6CF5FBD0F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 11 Apr 2022, at 19:53, Fernando Apestegu=C3=ADa <fernape@freebsd.org> = wrote: >=20 > On Mon, Apr 11, 2022 at 7:24 PM <jbo@insane.engineer> wrote: ... >> gmake[1]: Entering directory = '/wrkdirs/usr/ports/sysutils/cpufetch/work/cpufetch-1.00' >> Makefile:38: Unsupported arch detected: i386. See = https://github.com/Dr-Noob/cpufetch#1-support >> Makefile:39: If your architecture is supported but the compilation = fails, please open an issue in = https://github.com/Dr-Noob/cpufetch/issues >> Makefile:40: *** Aborting compilation. Stop. >> gmake[1]: Leaving directory = '/wrkdirs/usr/ports/sysutils/cpufetch/work/cpufetch-1.00' >> =3D=3D=3D> Compilation failed unexpectedly. >> Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the = failure to >> the maintainer. >> *** Error code 1 >>=20 >> Upstream's Makefile uses $(shell uname -m) to determine the = architecture [2]. My VMs are successfully reporting this as >> i386 which upstream's Makefile appears to support explicitly. After = all, I'm also able to build this software >> on those VMs if just cloning & running gmake manually. >>=20 >> I'm not really sure where to go from here. As I can build the = software in FreeBSD i386 VMs I think >> that the issue is related to my port and not upstream. But then = again, the build fails "within" upstream's Makefile. >>=20 >> Could somebody help me out here? >=20 > When the Makefile checks the output of uname -m, it compares the > result with a list of values that includes i686 but not i386. > I think a simple REINPLACE_CMD would suffice here. >=20 > Since I failed to detect this, do you want me to fix it in the repo? I > will also send a patch upstream. No need :) = https://github.com/Dr-Noob/cpufetch/commit/0db9f1f5c26e57a6383f4609c5605ed= 5d3d41fd1 -Dimitry --Apple-Mail=_BDE2D2B4-A84C-4271-85C2-60B6CF5FBD0F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCYlRr8QAKCRCwXqMKLiCW o/o7AJ92SRwkpsm226FP0/9q2aBfULP0qwCgoBifk/6gc5K77hqg5qkkbltm1O0= =4O5L -----END PGP SIGNATURE----- --Apple-Mail=_BDE2D2B4-A84C-4271-85C2-60B6CF5FBD0F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?168EF37D-8591-4F8C-93E1-F15FDA10F311>