zsh-users
 help / color / mirror / code / Atom feed
From: Josh Howard <jrh@vicor-nb.com>
To: Roland Jesse <jesse@mail.CS.Uni-Magdeburg.De>
Cc: ZSH Mail List <zsh-users@sunsite.auc.dk>, shige@FreeBSD.org
Subject: Re: zsh: failed to load module: zle
Date: 07 Jan 2000 14:46:17 -0800	[thread overview]
Message-ID: <yfgg0w9wldy.fsf@kashmir.vicor-nb.com> (raw)
In-Reply-To: Roland Jesse's message of "07 Jan 2000 11:26:38 +0100"

Sure you didn't use the 3.1.6 package? The port will work fine, but
the package probably won't.

Roland Jesse <jesse@mail.CS.Uni-Magdeburg.De> writes:

> Using the zsh 3.1.6 port on a fresh FreeBSD 3.4R machine leaves me
> with the impossibility to load the zle module.
> 
> The machine: 
> 
> % uname -a
> FreeBSD  3.4-RELEASE FreeBSD 3.4-RELEASE #0: Thu Jan  6 19:31:03 CET 2000     root@:/usr/src/sys/compile/ARTHUR  i386
> 
> The problem:
> 
> % zmodload zle
> zsh: failed to load module: zle
> % echo $module_path
> /usr/local/lib/zsh/3.1.6
> % pwd
> /usr/local/lib/zsh/3.1.6
> % file zle.so
> zle.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), stripped
> % zmodload -e
> zsh
> comp1
> % zmodload -ab
> ulimit (rlimits)
> zle
> sched
> compctl
> compadd (compctl)
> compset (compctl)
> limit (rlimits)
> vared (zle)
> compgen (compctl)
> unlimit (rlimits)
> 
> Loading other modules works fine:
> % zmodload example
> The example module has now been set up.
> 
> I would appreciate any pointers on whether or not this might be a
> specific problem with the FreeBSD port.
> 
> Thanks.
> 		Roland
> 

-- 
Josh Howard <jrh@vicor-nb.com>


      parent reply	other threads:[~2000-01-07 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-07 10:26 Roland Jesse
2000-01-07 15:20 ` Clint Adams
2000-01-08 10:37   ` Roland Jesse
2000-01-08 15:14     ` Shigeyuki Fukushima
2000-01-08 22:10       ` Josh Howard
2000-01-07 22:46 ` Josh Howard [this message]

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=yfgg0w9wldy.fsf@kashmir.vicor-nb.com \
    --to=jrh@vicor-nb.com \
    --cc=jesse@mail.CS.Uni-Magdeburg.De \
    --cc=shige@FreeBSD.org \
    --cc=zsh-users@sunsite.auc.dk \
    /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).