Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rDSxk-0026QT-5s for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Dec 2023 17:24:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rDSxh-00FyV7-Sf for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Dec 2023 17:23:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rDSxh-00FyUw-I8 for pgsql-hackers@lists.postgresql.org; Wed, 13 Dec 2023 17:23:57 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rDSxe-00BpDy-Ku for pgsql-hackers@postgresql.org; Wed, 13 Dec 2023 17:23:56 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3ba00fe4e94so3307633b6e.1 for ; Wed, 13 Dec 2023 09:23:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neon.tech; s=google; t=1702488232; x=1703093032; darn=postgresql.org; h=in-reply-to:references:subject:cc:from:to:message-id:date :content-transfer-encoding:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ZgrRlhVmW4NDnGg7fgmEMDwHjZH+Y8iu4+QbMGh/mAw=; b=p79Ars6gvzSSparCgcKa7TkI0v/lHeQXTVd/RO5k/nnb0myGQt0NGMmy77QGd4e2mS Q3bbC9uGLa3IyxYhLXNXkHOWYcXqBJEtMPcvp/tT7a4aWH6r3Bs+koD09v40XH9Pf7Lh pT1ZMb4Obdobt7weGh9vRAqjkCbRROewZs5nI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702488232; x=1703093032; h=in-reply-to:references:subject:cc:from:to:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ZgrRlhVmW4NDnGg7fgmEMDwHjZH+Y8iu4+QbMGh/mAw=; b=QMFGhCkfhWiQ6ESSrd+4nP9SMSKqtQFb8qkvWUyCIbO+iiIeKTa01vtdVXiJiBt9Bw 6rZQLqqDoIl5YLUGbj8MKmabNo/Yz0deoxvvlh4IL7A3YQIpTngCUT1MjzppSKhxzBab ri926Cg8Kyr3mvKuAEC7bWgJiiW3Jl1WZNn3cPWAgYw/NFZ55oAfQFytGQPWaTfZlz6V 5A4e+0bnyPGRhm4UIYB+vLm/2k0avmZ8XFphBPhtoRo6n01A1JqtYUwY7SpGf5veQrG3 SNMpLm/1/RTpgo0CNLeew89AdQK1fWO5xxPqe1pbGcsgWMDy86cWnILZ7tmx0nbuxyi5 i//g== X-Gm-Message-State: AOJu0Yw74LDgZg/kEtZowuwKVyMlOX5gf456mmnxPF1DpDyxefBKECLz j9/eIghRnKCWJKSiBrD2YgMYzw== X-Google-Smtp-Source: AGHT+IFLt02Hi8fLANjIgGjDSNJN9qisjbTgV9JBr4T0TxyvUKHPvuNUf0zlnMW4vn4iKxi1WyM5bg== X-Received: by 2002:a05:6808:eca:b0:3b8:b063:9b70 with SMTP id q10-20020a0568080eca00b003b8b0639b70mr9374196oiv.98.1702488231878; Wed, 13 Dec 2023 09:23:51 -0800 (PST) Received: from localhost ([2607:fb90:e64f:544c:3996:e070:71ee:42fb]) by smtp.gmail.com with ESMTPSA id 6-20020aca0f06000000b003b8b28a3ef6sm3007907oip.14.2023.12.13.09.23.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Dec 2023 09:23:51 -0800 (PST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8; format=Flowed Date: Wed, 13 Dec 2023 11:23:50 -0600 Message-Id: To: "Tom Lane" From: "Tristan Partin" Cc: , "Andrew Dunstan" Subject: Re: Clean up find_typedefs and add support for Mac X-Mailer: aerc 0.16.0-91-g2db657b6bdd6 References: <2490307.1702422146@sss.pgh.pa.us> In-Reply-To: <2490307.1702422146@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue Dec 12, 2023 at 5:02 PM CST, Tom Lane wrote: > "Tristan Partin" writes: > > The big patch here is adding support for Mac. objdump -W doesn't work o= n=20 > > Mac. So, I used dsymutil and dwarfdump to achieve the same result. > > We should probably nuke the current version of src/tools/find_typedef > altogether in favor of copying the current buildfarm code for that. > We know that the buildfarm's version works, whereas I'm not real sure > that src/tools/find_typedef is being used in anger by anyone. Also, > we're long past the point where developers can avoid having Perl > installed. > > Ideally, the buildfarm client would then start to use find_typedef > from the tree rather than have its own copy, both to reduce > duplication and to ensure that the in-tree copy keeps working. That makes sense to me. Where can I find the buildfarm code to propose=20 a different patch, at least pulling in the current state of the=20 buildfarm script? Or perhaps Andrew is the best person for this job. --=20 Tristan Partin Neon (https://neon.tech)