From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18811 invoked by alias); 17 Jan 2015 04:00:02 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 34317 Received: (qmail 9201 invoked from network); 17 Jan 2015 03:59:49 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Authority-Analysis: v=2.1 cv=T/C1EZ6Q c=1 sm=1 tr=0 a=e1dXK7GfYbHG4k4nVCYCAw==:117 a=e1dXK7GfYbHG4k4nVCYCAw==:17 a=Hpgzp-inWqAA:10 a=N659UExz7-8A:10 a=KymbNnWKjgxqPb_QfFcA:9 a=pILNOxqGKmIA:10 Message-id: <54B9D726.2020108@eastlink.ca> Date: Fri, 16 Jan 2015 19:29:42 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.3.0 MIME-version: 1.0 To: zsh-workers@zsh.org Subject: Re: Command substitution parsing issues (not really Re: completion) References: <54B9AA99.6080403@eastlink.ca> <150116185732.ZM30791@torch.brasslantern.com> In-reply-to: <150116185732.ZM30791@torch.brasslantern.com> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 01/16/2015 06:57 PM, Bart Schaefer wrote: > On Jan 16, 4:19pm, Ray Andrews wrote: > } > } $ ln -svf zsh-5.0.7-175-./Src/zsh: symbol lookup error: > } /usr/local/lib/zsh/5.0.7-dev-0/zsh/zle.so: undefined symbol: lexsave > > You need to re-install the shared object files. The symbols have in > fact changed, you're loading a .so from a previous build. Ok, I thought that might be the case. An unidentified symbol would not survive the developer's build of his own work. > > In fact if you're going to live on the bleeding edge of git pull, you > should have a separate shared-object directory for every build. Can you suggest a method? It's easy enough to save old kernels, but the rest of zsh's various files here and there are still a mystery. I didn't even know there were library files like that. Does 'git pull; make -s' even update those? Seems not. There are variables pointing to the locations of these support files, yes? If so, I can easily create numbered directories for the files and then ... well, whatever you recommend.