Re: configure --with-uuid=bsd fails on NetBSD

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: configure --with-uuid=bsd fails on NetBSD
Date: 2022-08-21 00:48:51
Message-ID: 20220821004851.5mc74mrqboxtq6d5@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-08-20 19:39:32 -0400, Tom Lane wrote:
> Our documentation claims that --with-uuid=bsd works on both
> FreeBSD and NetBSD: installation.sgml says
>
> <option>bsd</option> 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.

Also recently reported as a bug: https://postgr.es/m/17358-89806e7420797025%40postgresql.org
with a bunch of discussion.

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

Perhaps we should make them error out instead? It doesn't seem helpful to
just return something wrong...

Certainly would be good to get the regression tests to pass somehow, given
that we don't expect this to work. Don't want to add netbsd's results as an
alternative, because that'd maybe hide bugs. But if we errored out we could
probably have an alternative with the errors, without a large risk of hiding
bugs.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-08-21 01:37:32 Re: configure --with-uuid=bsd fails on NetBSD
Previous Message Andres Freund 2022-08-21 00:42:34 Re: [RFC] building postgres with meson