From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-44746-ml=inbox.vuxu.org@zsh.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no
	version=3.4.2
Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id 0adbfe2e
	for <ml@inbox.vuxu.org>;
	Tue, 10 Sep 2019 03:21:27 +0000 (UTC)
Received: (qmail 16971 invoked by alias); 10 Sep 2019 03:21:21 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 44746
Received: (qmail 22159 invoked by uid 1010); 10 Sep 2019 03:21:21 -0000
X-Qmail-Scanner-Diagnostics: from mail-lf1-f47.google.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.101.2/25566. spamassassin: 3.4.2.  
 Clear:RC:0(209.85.167.47):SA:0(-1.9/5.0):. 
 Processed in 1.802488 secs); 10 Sep 2019 03:21:21 -0000
X-Envelope-From: schaefer@brasslantern.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.167.47 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=brasslantern-com.20150623.gappssmtp.com; s=20150623;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=W5EzGguxGTp9xUc64L4CdqhUMQ+Gme7put4m75CnzWo=;
        b=VlhI7uMWlXD7qPA4iYn943i/nDoY8jiP8KihkrGJqcB4ig5vAZbU7uroG9vOxJM4Rb
         eO9HwrCXsYctI+c5L9TNVy5YymCsCavi8IzzYDpORU5aBxg3ib1/GlFBQm4BlpkPJyMz
         bzfMB4RzIJQpb5oUdWDTVhAOkOh3pQsYnAj4fY3EOFmf1F2INqqEMpIVY87QKLG88LvC
         JZ29iFTUIDmdd2m/R9BAjgFAybMEpArmVFmIerF84X2K9vxXasxKWbHcK83f+sW4r0S1
         Owbb0GXBmcPtf2ahkLaHa+D3nwgVf0Gb+0Ly+tSWzJH6I5j4GmEelNMG9SvUV+hwQ3qe
         qznA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=W5EzGguxGTp9xUc64L4CdqhUMQ+Gme7put4m75CnzWo=;
        b=mqcWXOe7vhhGhJRn4lIg1I/8eR8P3fwRtxlUvrkkQcpXY+EfRXKa0swzlrE/7E5IcV
         h+xumqkPzMtDa/R0gJmXcOyQTWDXIU+ebFogpgMBYOsDIJsowjobcrOQEnNUPi35qNAT
         tnyRKX6vzsT+ks9QlG7xAP140TkT5PlG/ThMTIvs0bRnw7TlQsTqdWYVaSYqbhqHr/Ps
         ubagRsrbYEEtq9E8p6IKWgZT0StOtWC/Sock9cj7wlLzJgfcRcB6QxgtNmRxTZ58Jc5e
         aDS+t0toEwoQMnPm5EeH3M7Qm7mXyfwVPuju9kJm1OhmZbsOfQvt/bbQa2xL8KFTIEWc
         AzUw==
X-Gm-Message-State: APjAAAU/ZBLhz3+/a0MxPumBz6/ohrke4mhOMYocKR+s8CSAbs0rtTjl
	rFn1zHXQKfvVvmkomSrdy6WdoObZQtktZxgt6d8WXf7t8WQ=
X-Google-Smtp-Source: APXvYqyHtK7/+hBH41MSdtSYo0N9y2216ezEStHNtnr88wGSafDBT0Kb768WXizFzQKLRtOOBHOjvBuyZqu0HQvQg48=
X-Received: by 2002:ac2:5a4c:: with SMTP id r12mr18390005lfn.52.1568085645203;
 Mon, 09 Sep 2019 20:20:45 -0700 (PDT)
MIME-Version: 1.0
References: <CAH+w=7aEfAgq6jfzWahm-OFBu2pXDCY6ZwfmvY-VWd8JGjVB6w@mail.gmail.com>
In-Reply-To: <CAH+w=7aEfAgq6jfzWahm-OFBu2pXDCY6ZwfmvY-VWd8JGjVB6w@mail.gmail.com>
From: Bart Schaefer <schaefer@brasslantern.com>
Date: Mon, 9 Sep 2019 20:20:33 -0700
Message-ID: <CAH+w=7Zmu7vVsC0L95095VvSWq2xpXM-0+y06Ma6KgbinHeA+Q@mail.gmail.com>
Subject: Re: Strange failure building latest zsh w/Xcode on MacOS
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"

Never mind, sort of.  There was a stray symlink in the root of my
source tree from testing some completion thing or other, and the build
process started pulling in files from the symlink.  If I figure out
where that came from (or anyone has a hint) I may try to get it not to
do that.