public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tristan Partin <[email protected]>
To: Tom Lane <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: [email protected]
Subject: Re: typedefs.list glitches
Date: Tue, 12 Dec 2023 09:37:29 -0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Thu May 12, 2022 at 4:21 PM CDT, Tom Lane wrote:
> I wrote:
> > every buildfarm member that's contributing to the typedefs list
> > builds with OpenSSL.  That wouldn't surprise me, except that
> > my own animal sifaka should be filling that gap.  Looking at
> > its latest attempt[1], it seems to be generating an empty list,
> > which I guess means that our recipe for extracting typedefs
> > doesn't work on macOS/arm64.  I shall investigate.
>
> Found it.  Current macOS produces
>
> $ objdump -W
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: error: unknown argument '-W'
>
> where last year's vintage produced
>
> $ objdump -W
> objdump: Unknown command line argument '-W'.  Try: '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump --help'
> objdump: Did you mean '-C'?
>
> This confuses run_build.pl into taking the "Linux and sometimes windows"
> code path instead of the $using_osx one.  I think simplest fix is to
> move the $using_osx branch ahead of the heuristic ones, as attached.

Hey Tom,

Was this patch ever committed?

-- 
Tristan Partin
Neon (https://neon.tech)

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: typedefs.list glitches
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox