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 1pbnSx-0003bc-Ng for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Mar 2023 19:04:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pbnSw-0007Ke-6L for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Mar 2023 19:04:14 +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 1pbnSv-0007KU-RA for pgsql-hackers@lists.postgresql.org; Mon, 13 Mar 2023 19:04:13 +0000 Received: from mail-pg1-x52a.google.com ([2607:f8b0:4864:20::52a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pbnSr-0002KC-Um for pgsql-hackers@postgresql.org; Mon, 13 Mar 2023 19:04:13 +0000 Received: by mail-pg1-x52a.google.com with SMTP id p6so7575670pga.0 for ; Mon, 13 Mar 2023 12:04:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678734247; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=O2HsqqoEYFtJN08UFZm+A3ASbFlF37iGGcIgeF9ksIc=; b=X4YhAncMrlwfBjf82Sh74q7eG8+keKK0OsCp1WtFhEEL/u4GJcZJ+5DTP7LXiEoCXi JRdSXa7e+koi9qf9wPgDPrn1+92MXe7eZv2m9KazJqKzZ7URR/QU2OneWIHVwY6Fpwb2 qbL/+e7OLHPrK2tEbp98/l/94Nzu6XnFgtER2+edaL5bM+y4PnyFEIkFG/JGeHy22dp5 lwLrxnFpb+jrB64SWdZLDxabz9wZhkWld9vuBeUJ1h3uKouv/4j3Z3KHPIBZL4OWqUdC lUUuhenJI/O0olpOBP/Te91wrVPqIMcOQhF3D0LI0QSx31KltNcm4OpBwwPSolqu8esr ftyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678734247; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=O2HsqqoEYFtJN08UFZm+A3ASbFlF37iGGcIgeF9ksIc=; b=x2sNyFC4dITHN3XzKbbFpU8Q4j5ASRSi3IagECAk+bNvkw8xnw4s5K0r0RvhzmDXTG 34ZqGom8EfSQNN6g/WKYYK2XmYRysahs+DzlNfEHJdbYnBH6qHz/CR1jH7FocSXiXL5t qQMvl3Ayg4p0ALNvY3QrEjORXf3u/ugrln+bPvUWrlJ3iftOLyoH8NcQ6Dc6sccT1x8b AyjlCj6ZHD3aXj2MZ6X6Vsfl+D85TwehKq/9rGwkpYTRRvdsUdQfuOT7nwyBeq2QA2A4 8x3eLLxSfq1UPHCUJgbjMAYDQEHgiYFz7qMmuJulpA3slOrYYZDcsB1mgcEVb9LR6pAL qn7w== X-Gm-Message-State: AO0yUKUj1KoiscnQNcsI+jw9b1H2b0zfHj6K+6v8E2e/9Em7qgbXx2ZP 80QJVPgJf9sA2UX75AIt7fc= X-Google-Smtp-Source: AK7set9nl1R60pfTVCsWOusW/Ty+nH+veaHAnG/oeFzw3VsTG+znOuykruAkOSdw735LO2F/uNg9wg== X-Received: by 2002:aa7:9629:0:b0:594:15fd:895e with SMTP id r9-20020aa79629000000b0059415fd895emr32826121pfg.31.1678734247598; Mon, 13 Mar 2023 12:04:07 -0700 (PDT) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id q25-20020a62e119000000b005810a54fdefsm75039pfh.114.2023.03.13.12.04.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Mar 2023 12:04:07 -0700 (PDT) Date: Mon, 13 Mar 2023 12:04:05 -0700 From: Nathan Bossart To: Nazir Bilal Yavuz Cc: Peter Eisentraut , Daniel Gustafsson , Andres Freund , PostgreSQL Hackers Subject: Re: meson: Non-feature feature options Message-ID: <20230313190405.GA342118@nathanxps13> References: <0fff0827-c1f5-d29c-2ee3-dc8c871176bf@enterprisedb.com> <9df9067d-5651-2d3e-e838-9e5d273f5524@enterprisedb.com> <5250E85B-4A97-4DA1-8900-7DCDE925441A@yesql.se> <6d3310fb-50e3-34d8-fe10-8dd8c4ffdf23@enterprisedb.com> <20230313180432.GA246741@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Mar 13, 2023 at 09:57:22PM +0300, Nazir Bilal Yavuz wrote: > On Mon, 13 Mar 2023 at 21:04, Nathan Bossart wrote: >> Shouldn't "auto" cause Postgres to be built without OpenSSL if the required >> headers are not present? > > Yes, I tested again and it is working as expected on my end. It > shouldn't fail like that unless the 'ssl' option is set to 'openssl'. > Is it possible that it has been set to 'openssl' without you noticing? I do not believe so. For the test in question, here are the build options reported in meson-log.txt: Build Options: -Dlz4=enabled -Dplperl=enabled -Dplpython=enabled -Dpltcl=enabled -Dlibxml=enabled -Duuid=ossp -Dlibxslt=enabled -Ddebug=true -Dcassert=true -Dtap_tests=enabled -Dwerror=True -- Nathan Bossart Amazon Web Services: https://aws.amazon.com