From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=FREEMAIL_FROM, 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 dbb1d216 for ; Sat, 7 Mar 2020 13:04:13 +0000 (UTC) Received: (qmail 11882 invoked by alias); 7 Mar 2020 13:04:06 -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: List-Unsubscribe: X-Seq: 45515 Received: (qmail 19783 invoked by uid 1010); 7 Mar 2020 13:04:06 -0000 X-Qmail-Scanner-Diagnostics: from mail-40130.protonmail.ch by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.2/25738. spamassassin: 3.4.2. Clear:RC:0(185.70.40.130):SA:0(-2.7/5.0):. Processed in 2.314619 secs); 07 Mar 2020 13:04:06 -0000 X-Envelope-From: codenb@protonmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.protonmail.ch designates 185.70.40.130 as permitted sender) Date: Sat, 07 Mar 2020 13:03:15 +0000 To: Bart Schaefer From: Coden Cc: "zsh-workers@zsh.org" Reply-To: Coden Subject: Re: Portable rootless ZSH Message-ID: In-Reply-To: <4XeMR-DaD1iuP2o6WRImZHS7lhiCE95A9Aq9OXj7DJPBwz6XC_6Lpxvw5m1VFfqgEDYSlRjPU01kXfBpHbv58VaUtsfUiD1788YZhpmBdOc=@protonmail.com> References: <20191008204722.GU6761@ming.fruitbat.org> <-1Pz0W4MKe73f-nCkejafEE_SNaTME3zWtRpz26zC_wtj9KNc0hpsLeZA60x2YG1GSs5D7RW10p5kfmsy5HRFiXl3oHHx3wt2NHVKUGfX_0=@protonmail.com> <4XeMR-DaD1iuP2o6WRImZHS7lhiCE95A9Aq9OXj7DJPBwz6XC_6Lpxvw5m1VFfqgEDYSlRjPU01kXfBpHbv58VaUtsfUiD1788YZhpmBdOc=@protonmail.com> Feedback-ID: 1g_EZM5cadEHcIg82x2qZXWXT-U_XXBlI7kN837NwaZpram7G2oom_E1e2DIYhFQFmC50rpRJhWFHjVSm_Y7-w==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Bart and all here! I'm back. Thank you for your help before! I've tried your recommendation but got an error: "./zsh: error while loading shared libraries: libtinfo.so.5: cannot open sh= ared object file: No such file or directory" 0. I've tried: zsh version: 5.7.1 OS where zsh is built: Ubuntu 16.04 OS where portable zsh is tested: Ubuntu 19.10 1. > ./configure --disable-dynamic --prefix=3D$PWD/run --bindir=3D$PWD/run > --enable-etcdir=3D./run/etc --enable-scriptdir=3D./run/scripts > --enable-fndir=3D./run/functions --enable-function-subdirs > --disable-site-fndir 2. >(edit config.modules) I've tried to make all modules "link=3Dstatic". I tried default. 3. > make && make install > cd run && ln -s . run && mkdir etc && cd .. 4. > Now you can move the "run" directory anywhere, even rename it provided > it contains the symlink "run" pointing to itself, and when you cd into > it and then execute "./zsh", everything works. There is one other > step needed: After moving/copying/whatever the "run" directory to its > final location, you have to create a zshenv file in that "etc" subdir > and assign fpath. You could also assign module_path for completeness, > but as noted nothing will ever use it. To assign the fpath you can > just do: > ./zsh -fc 'typeset -p fpath' | sed "s,./run,$PWD,g" > etc/zshenv The ./zsh is working on Ubuntu 16.04 where it built. But when I moved run directory to Ubuntu 19.10 I've got an error: "./zsh: error while loading shared libraries: libtinfo.so.5: cannot open sh= ared object file: No such file or directory" Could you please advise what I'm doing wrong? May be I should build zsh on = special Linux version or update to zsh 5.8? Thank you for the response! =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Monday, October 14, 2019 2:51 AM, Coden wrote: > Thank you for details! I'll try again. > > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original = Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 > On Sunday, October 13, 2019 8:59 AM, Bart Schaefer schaefer@brasslantern.= com wrote: > > > On Sat, Oct 12, 2019 at 5:13 PM Coden codenb@protonmail.com wrote: > > > > > I don't understand one thing. I want to build rootless binary. > > > > > > - When I wrote that there is a way to build the binary on old versi= on of packages I mean that library version checking raises the error only i= f the current packages version is older than used when compile. This workar= ound allows me to imitate "rootless" and I've tested my binary on modern li= nux distros versions and it works. > > > > "Your mileage may vary" but typically if you want a fully portable > > binary you need to static link everything. Otherwise you're > > eventually going to run into some kind of dynamic linkage problem, > > even it it seems currently to work to compile with an older shared > > object and then run with a newer one. > > > > > - But when you wrote about prefix-like flags I think you understand= that prefix-like flags requres absolute path from root like /usr/share. It= 's not rootless behaviour. Yes we can change prefixes for lib paths on buil= ding but we can't make it relative. I'm wrong? > > > > Only a couple of them require an absolute path, and ultimately that > > only matters to "make install" (it changes $module_path but all of > > your modules are static). Some variation of this seems to work: > > ./configure --disable-dynamic --prefix=3D$PWD/run --bindir=3D$PWD/run > > --enable-etcdir=3D./run/etc --enable-scriptdir=3D./run/scripts > > --enable-fndir=3D./run/functions --enable-function-subdirs > > --disable-site-fndir > > (edit config.modules) > > make > > make install > > cd run > > ln -s . run > > mkdir etc > > cd .. > > Now you can move the "run" directory anywhere, even rename it provided > > it contains the symlink "run" pointing to itself, and when you cd into > > it and then execute "./zsh", everything works. There is one other > > step needed: After moving/copying/whatever the "run" directory to its > > final location, you have to create a zshenv file in that "etc" subdir > > and assign fpath. You could also assign module_path for completeness, > > but as noted nothing will ever use it. To assign the fpath you can > > just do: > > ./zsh -fc 'typeset -p fpath' | sed "s,./run,$PWD,g" > etc/zshenv > > and now you're all set. > > > > > What step in your way gives us relativity? > > > > The problem with your scheme is that anything loaded at run time -- > > such as the completion functions -- HAS to be loaded by absolute path, > > in order for the shell to ever be able to change directory. That's > > why normally one would instead create a zsh package that was intended > > always to be installed in a predetermined fixed location, and use the > > configure options to set the default paths to that fixed place. This > > is the procedure my previous message was describing.