Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oPY42-0001YU-Mt for pgsql-hackers@arkaria.postgresql.org; Sat, 20 Aug 2022 23:39:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oPY41-0005iZ-7q for pgsql-hackers@arkaria.postgresql.org; Sat, 20 Aug 2022 23:39:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oPY40-0005iQ-UX for pgsql-hackers@lists.postgresql.org; Sat, 20 Aug 2022 23:39:36 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oPY3y-0005cZ-Sj for pgsql-hackers@lists.postgresql.org; Sat, 20 Aug 2022 23:39:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 27KNdW9K3848060 for ; Sat, 20 Aug 2022 19:39:32 -0400 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: configure --with-uuid=bsd fails on NetBSD MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3848058.1661038772.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 20 Aug 2022 19:39:32 -0400 Message-ID: <3848059.1661038772@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Our documentation claims that --with-uuid=3Dbsd works on both FreeBSD and NetBSD: installation.sgml says to use the UUID functions found in FreeBSD= , NetBSD, and some other BSD-derived systems and there is comparable wording in uuid-ossp.sgml. In the course of setting up a NetBSD buildfarm animal, I discovered that this is a lie. NetBSD indeed has the same uuid_create() function as FreeBSD, but it produces version-4 UUIDs not version-1, which causes the contrib/uuid-ossp regression tests to fail. You have to dig down a level to the respective uuidgen(2) man pages to find documentation about this, but each system appears to be conforming to its docs, and the old DCE standard they both refer to conveniently omits saying anything about what kind of UUID you get. So this isn't a bug as far as either BSD is concerned. I'm not personally inclined to do anything about this; I'm certainly not excited enough about it to write our own v1-UUID creation code. Perhaps we should just document that on NetBSD, uuid_generate_v1() and uuid_generate_v1mc() don't conform to spec. regards, tom lane