Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Dec 2017 00:29: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:  <1b69f03c-fe9f-ad9f-a314-395c713d2329@schonrocks.com>
In-Reply-To: <20171211234106.GP1783@over-yonder.net>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tTnaaA0vWc8GR19KGkGa7bgD3Bc0Q9sgb
Content-Type: multipart/mixed; boundary="A8J4SrMmM4rdRue3pBrke2EaURN9iwHXR";
 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: <1b69f03c-fe9f-ad9f-a314-395c713d2329@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>
In-Reply-To: <20171211234106.GP1783@over-yonder.net>

--A8J4SrMmM4rdRue3pBrke2EaURN9iwHXR
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable

On 11/12/17 23:41, Matthew D. Fuller wrote:
> On Mon, Dec 11, 2017 at 11:32:08PM +0000 I heard the voice of
> Oliver Schonrock, and lo! it spake thus:
>> and it solves my issue as well.  Don't think the CPUTYPE stuff comes
>> into it.
> Well, maybe.  From your mail, though, it looks like you did that
> testing by rebuilding/installing the ports _on the local machine_,
> rather than rebuilding in poudriere.  If the poudriere box was
> building binaries with instructions not in your local machine, that
> local build would bypass that issue, so it may still be there.
> "Illegal instruction" seems like an odd presentation for "missing
> file".

It's a good point, I get ya. You're right, I did not retest the
poudriere build.

The Poudriere machine has a:

Intel(R) Core(TM) i3-4130T: Haswell (4th gen)

The machine that is throwing the "Illegal instruction" error, is a
VirtualBox VM running on an:
Intel(R) Core(TM) i7-2600 CPU: Sandy Bridge (2nd gen)

Our production machines are all:
CPU: AMD Opteron(tm) Processor 4386: "Seoul" (32 nm)

Ideally I would like to be able to use the packages built by the i3-4130
machine to run without hitches across all 3 CPU types, while still
taking advantage of their features for openssl/TLS, etc.

What would be a good CPUTYPE line for make.conf?

I am non-the-wiser from the docs in /usr/share/examples/etc/make.conf


--=20
Oliver Sch=C3=B6nrock
Mobile   : +44 7880 617 446
email    : oliver@schonrocks.com


--A8J4SrMmM4rdRue3pBrke2EaURN9iwHXR--

--tTnaaA0vWc8GR19KGkGa7bgD3Bc0Q9sgb
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

iQEcBAEBCAAGBQJaLyLpAAoJEF6SumULDx4PunsIAKR+95HByRwyeXjgr7xjzLWr
KzRhUl+fcyJdL1QcvskDEY3m8sEkS03KWwUgWaWb6K2tIozhfvpXpP8dNgmjrxFW
kczakGbXXgwIwjrnFtQ2a7C72+jFjqFi8VfxC8XvEHNostxEyX3GhLd3L3DR1xNX
WgQylKRFRxdzZzkAu4AVrrtOHxgvHuPxAP52t/PvlDuNekL5/kOoCwNbTSln4mzx
RGpcGxHoGuPy+8u6nrDAjw8ls0i6Tt3RSE71LPNmaF4DdnGR4ueUByUibDHOyGI2
8KljCMhYe1AD+xVKBumcbjPMfxRy1aAHhqbNHmkNhtUgzTZeuqBrhgzuZPNE9l8=
=448B
-----END PGP SIGNATURE-----

--tTnaaA0vWc8GR19KGkGa7bgD3Bc0Q9sgb--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1b69f03c-fe9f-ad9f-a314-395c713d2329>