From: Coden <codenb@protonmail.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Portable rootless ZSH
Date: Sat, 12 Oct 2019 21:22:39 +0000 [thread overview]
Message-ID: <q9STAY5-iaqPtJEpUF1qCIiTR8Oc-8p6fuuvMvSuAlI_PE0gRpzNeAzg8bjdaTT6lDm4lIufqeqVSuqVbj0RLszcohztg3kmVBlLykeyPcs=@protonmail.com> (raw)
In-Reply-To: <FG_5iNx0DPNq-a1zqxGntg3hmpbHyJ_zHKFQZKw-LyXw5ee11rRK_98EM8usgD307Kld2pofl-KsvmWOeMBiQ37j_fwRxcA0oZbNM_6NZ2U=@protonmail.com>
> ./zsh: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./zsh)
The solution is to build zsh on older version of packages (in Ubuntu 14 for example).
Thanks to all! It seems I built what I need.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, October 11, 2019 10:32 PM, Coden <codenb@protonmail.com> wrote:
> Hi Peter!
>
> > The directories are given by fpath (array) and FPATH
>
> Thank you for link to FPATH! It is one step forward for me. But I've faced with error.
>
> When I try to rebuild and run zsh on the server where zsh was installed I've got success:
>
> 1. Build ./configure --disable-dynamic --disable-gdbm && make
> 2. export FPATH="/home/user/.autojump/functions:/home/user/.oh-my-zsh/plugins/git:/home/user/.oh-my-zsh/functions:/home/user/.oh-my-zsh/completions:/usr/local/share/zsh/site-functions:/usr/share/zsh/vendor-functions:/usr/share/zsh/vendor-completions:/usr/share/zsh/functions/Calendar:/usr/share/zsh/functions/Chpwd:/usr/share/zsh/functions/Completion: ......"
> 3. Run ./Src/zsh
> 4. It works as expected with OMZ theme!
>
> But when I copy ./Src/zsh with all FPATH directories to another server where ZSH has never been installed I've got the error:
>
> $ export FPATH="..."
> $ ./zsh
> ./zsh: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./zsh)
>
> Coden
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
>
> > > From: Peter Stephenson p.stephenson@xxxxxxxxxxx
> > > On Wed, 2019-10-09 at 20:07 +0000, Coden wrote:
> > >
> > > > /root/.oh-my-zsh/oh-my-zsh.sh:69: compinit: function definition file not found
> > > > /root/.oh-my-zsh/lib/theme-and-appearance.zsh:2: colors: function definition file not found
>
> > > OK, so assuming the static linking is all set up (it's certainly doable
> > > but not necessarily trivial as it's not all that common these days),
> > > you're now faced with making shell functions available. These can live
> > > anywhere --- nothing here needs to be set up as root --- but obviously
> > > you need to put them somewhere, and then tell the shell where you've put
> > > them. The directories are given by fpath (array) and FPATH
> > > (collon-separated values for putting into the environment). You can
> > > look at the existing values for an idea of where everything is on the
> > > system you're starting from. Probably you'll be configuring the
> > > directories in ~/.zshenv in the target system.
> > > pws
next prev parent reply other threads:[~2019-10-12 21:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 18:44 Coden
2019-10-08 20:47 ` Peter A. Castro
2019-10-09 20:07 ` Coden
2019-10-11 11:54 ` Coden
2019-10-11 19:32 ` Coden
2019-10-12 21:22 ` Coden [this message]
2019-10-12 23:22 ` Bart Schaefer
2019-10-13 0:13 ` Coden
2019-10-13 5:59 ` Bart Schaefer
2019-10-13 23:51 ` Coden
2020-03-07 13:03 ` Coden
2019-10-11 13:11 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='q9STAY5-iaqPtJEpUF1qCIiTR8Oc-8p6fuuvMvSuAlI_PE0gRpzNeAzg8bjdaTT6lDm4lIufqeqVSuqVbj0RLszcohztg3kmVBlLykeyPcs=@protonmail.com' \
--to=codenb@protonmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).