Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gCNyF-0005BZ-9o for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Oct 2018 11:57:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gCNyD-0006K9-LP for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Oct 2018 11:57:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gCNyC-0006K2-O9 for pgsql-hackers@lists.postgresql.org; Tue, 16 Oct 2018 11:57:05 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gCNy3-0001tY-N8 for pgsql-hackers@lists.postgresql.org; Tue, 16 Oct 2018 11:57:04 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9B5ED22171; Tue, 16 Oct 2018 07:56:52 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 16 Oct 2018 07:56:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=y3RPH4jp+gxd91e7qHtp/0XKj4aGsJjX0I4eiLn6G aw=; b=GK5eUH32ZNKU3GBP70q/e14702y4987xhXma+y5d+Bun6EvZbQVliiLVg UUBU8Rd2XGGRHxJE9jF2yXTQu3hyaZo7MNMpXCzzstUkSndr2AHeBAOh2Eb5y0C3 fS33ixHhmD2i2/Dw9ob6hdfLUYJV9VloK07pT5F+ypQVVM/wB+eS77CI110L8IIV SYxljwMMH8j/vEczhWSIGJTGv1AV5CO0N4rzCPAPNpVVZ4OWfrj0ycoCCWY31Z8H IN2RNCBErSJJ6cKrxucMhjYQABLFUOmEd+W8lC6/5NTci2paQWxz1qupnvKo9raJ q9DkyHCMsM70tOCmpf9pU+Os82QLQ== X-ME-Sender: X-ME-Proxy: Received: from [192.168.77.107] (cpe90-146-112-58.liwest.at [90.146.112.58]) by mail.messagingengine.com (Postfix) with ESMTPA id 59180102EC; Tue, 16 Oct 2018 07:56:51 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: PG vs macOS Mojave From: Jakob Egger In-Reply-To: <20840.1537850987@sss.pgh.pa.us> Date: Tue, 16 Oct 2018 13:56:49 +0200 Cc: pgsql-hackers@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20840.1537850987@sss.pgh.pa.us> To: Tom Lane X-Mailer: Apple Mail (2.3445.100.39) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Am 25. Sep. 2018 um 06:49 schrieb Tom Lane : > It's a bit scary to be adding -isysroot globally. > (...) > I've tested this on all the macOS versions I have at hand, and it > doesn't seem to break anything. =20 > (...) > Thoughts? >=20 > regards, tom lane This breaks building extensions with a different SDK than the server = itself. Previously, it was possible for users to download a binary PostgreSQL = distribution and build an extension just by typing 'make install'. Now pgxs/src/makefile.global contains -isysroot of the machine where = PostgreSQL was built. If they use a different version of Xcode, or if = they renamed Xcode (I often use multiple versions side by side), = compilation will fail. As a workaround for Postgres.app, I've tried setting PG_SYSROOT to = /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Devel= oper/SDKs/MacOSX.sdk (which is a symlink to the current SDK). This = allows building extensions on a newer OS than what I use for building = the server, but if the user renames Xcode that still doesn't help. Jakob=