Date: Tue, 12 Dec 2017 11:03:29 +0000 From: Oliver Schonrock <oliver@schonrocks.com> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: ports <ports@FreeBSD.org>, tz@FreeBSD.org Subject: Re: FreeBSD Port: php72-7.2.0 : trouble with lang/php72 & libargon2 Message-ID: <9cae9f73-38da-2f83-297b-018ac452cfac@schonrocks.com> In-Reply-To: <d77a1139-7482-8686-bc3f-33ab76244bec@schonrocks.com> References: <6a2752ce-ee15-84a4-bd2b-150f614cf1a2@schonrocks.com> <20171211232847.GO1783@over-yonder.net> <9b51f4f4-8380-9bd3-37ee-e166939c16c4@schonrocks.com> <20171211234106.GP1783@over-yonder.net> <1b69f03c-fe9f-ad9f-a314-395c713d2329@schonrocks.com> <d77a1139-7482-8686-bc3f-33ab76244bec@schonrocks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MujTsOooGMV3jkvGu7VlggqNwNuKmv41m
Content-Type: multipart/mixed; boundary="gfntvKfKhnEsFkH83DwBiGJ1mSRXaovi1";
protected-headers="v1"
From: Oliver Schonrock <oliver@schonrocks.com>
To: "Matthew D. Fuller" <fullermd@over-yonder.net>
Cc: ports <ports@FreeBSD.org>, tz@FreeBSD.org
Message-ID: <9cae9f73-38da-2f83-297b-018ac452cfac@schonrocks.com>
Subject: Re: FreeBSD Port: php72-7.2.0 : trouble with lang/php72 & libargon2
References: <6a2752ce-ee15-84a4-bd2b-150f614cf1a2@schonrocks.com>
<20171211232847.GO1783@over-yonder.net>
<9b51f4f4-8380-9bd3-37ee-e166939c16c4@schonrocks.com>
<20171211234106.GP1783@over-yonder.net>
<1b69f03c-fe9f-ad9f-a314-395c713d2329@schonrocks.com>
<d77a1139-7482-8686-bc3f-33ab76244bec@schonrocks.com>
In-Reply-To: <d77a1139-7482-8686-bc3f-33ab76244bec@schonrocks.com>
--gfntvKfKhnEsFkH83DwBiGJ1mSRXaovi1
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable
On 12/12/17 10:26, Oliver Schonrock wrote:
> It seems that this file has the
> answer:
>=20
> /usr/src/share/mk/bsd.cpu.mk
>=20
=2E..
>=20
> So I should be able to put CPUTYPE=3Dsandybridge into /etc/make.conf
> and...happy days? No more nasty surprises?
Actually I am not entirely convinced that will work
eventhough /usr/src/share/mk/bsd.cpu.mk does a lovely job of defining
MACHINE_CPU based on what CPUTYPE we put in /etc/make.conf, it does not
appear that this value actually gets user (ie translated into CFLAGS). I
couldn't find anything in /usr/src or /usr/ports which uses MACHINE_CPU.
=46rom a comment at bottom of /usr/src/share/mk/sys.mk, it seems that thi=
s
is the responsibility of the ports themselves:
# Hack for ports compatibility. Historically, ports makefiles have
# assumed they can examine MACHINE_CPU without including anything
# because this was automatically included in sys.mk. For /usr/src,
# this file has moved to being included from bsd.opts.mk. Until all
# the ports files are modernized, and a reasonable transition
# period has passed, include it while we're in a ports tree here
# to preserve historic behavior.
and indeed some ports do that, eg
/usr/ports/security/cryptopp/Makefile
=2E if ${MACHINE_CPU:Msse2}
USES+=3D compiler:c++14-lang
CXXFLAGS+=3D -msse2
yet security/libargon2 does not reference MACHINE_CPU at all.
So it might be all for nought?
Does the port maintainer for security/libargon2 need to add such a
CFLAGS switch based on MACHINE_CPU into the Makefile?
Or is there some "magic" which feeds the "feature info" from MACHINE_CPU
into clang via CFLAGS (or some other way) automatically and my grep'ing
didn't find it?
--=20
Oliver Sch=C3=B6nrock
email : oliver@schonrocks.com
--gfntvKfKhnEsFkH83DwBiGJ1mSRXaovi1--
--MujTsOooGMV3jkvGu7VlggqNwNuKmv41m
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
iQEcBAEBCAAGBQJaL7eBAAoJEF6SumULDx4Pqq8H/jspedNoDl0gB58/newowEuL
FFrbB9X123VEz7JlnLQ6tiwP+kwGSxVSZQAAUkJP+Xh7nlEmVfJmrRMBug7B3T1m
K3VuaEp8dvNsyDywG7hbdu977xhJQqPN+eNdES2Z/gq+quPjRAtqXDuiY+k76pLf
hx4fP1C1XyCmrjBG2luyRxLeNGL/mZwlFA/kk4s7HEeN/vKJKAPi1QkqITnhMnzR
mLKdDhXtrI+EIvgsWklQmtTIXZ9qqDUa1QKOPNaVtFgPcdd+XVrex0bLyIXPanWF
GR5ZISc+NjpBYDvKBUgUnRn0LjZcXiYUqx/V1edbRpBWX2VeF2ptOg2Nx6DMfPA=
=6HvT
-----END PGP SIGNATURE-----
--MujTsOooGMV3jkvGu7VlggqNwNuKmv41m--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9cae9f73-38da-2f83-297b-018ac452cfac>