Re: Problems with modules and zsh 4.0.4

Re: Problems with modules and zsh 4.0.4

[Raúl Núñez de Arenas Coronado]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

    Hello all :)

>> the problems. Now, I don't know if these problems come from zsh
>> or gcc 3.0.
>This comes from GCC (or to be precise, from the particular configuration).

    Unfortunately, this is true...

>We already had the case. gcc-3 compiled programs need extra shared
>library (I forgot the name).

    libgcc_s.so. I don't really know what's the point with this
library :??? I should read the FAQ's for GCC.

    Anyway I have zsh 4.0.4 compiled with GCC 3.0.1 and it seems to
work ok (I have detected no flaws by now, at least).

    Raúl

Problems with modules and zsh 4.0.4

[Vincent Lefevre]

I've just compiled and installed zsh 4.0.4 on the following machine:

Linux greux.loria.fr 2.2.17 #13 SMP Tue Dec 12 15:26:51 MET 2000 i686 unknown

But when I rlog to this machine, I get errors like:

/users/spaces/lefevre/.zshrc:54: failed to load module: zsh/rlimits
/users/spaces/lefevre/.zshrc:limit:54: autoload failed
/users/spaces/lefevre/.zshrc:104: failed to load module: zsh/parameter
/users/spaces/lefevre/.zshrc:305: failed to load module: zsh/zle
/users/spaces/lefevre/.zshrc:bindkey:305: autoload failed
/users/spaces/lefevre/.zshrc:306: command not found: bindkey
/users/spaces/lefevre/.zshrc:307: command not found: bindkey
[...]

However, if I exec $SHELL after rlogging, I no longer get such
problems. With zsh 4.0.2, there were no problems at all.

zsh configuration
-----------------
zsh version               : 4.0.4
host operating system     : i686-pc-linux-gnu
source code location      : .
compiler                  : gcc
preprocessor flags        : -I/users/spaces/lefevre/include
executable compiler flags :  -Wall -Wno-implicit -Wmissing-prototypes -O2
module compiler flags     :  -Wall -Wno-implicit -Wmissing-prototypes -O2 -fPIC
executable linker flags   : -L/users/spaces/lefevre/i686-linux/lib -L/users/spaces/lefevre/lib  -rdynamic
module linker flags       : -L/users/spaces/lefevre/i686-linux/lib -L/users/spaces/lefevre/lib  -shared
library flags             : -ldl -lnsl -lcurses -lm  -lc
installation basename     : zsh
binary install path       : /users/spaces/lefevre/i686-linux/bin
man page install path     : /users/spaces/lefevre/man
info install path         : /users/spaces/lefevre/info
functions install path    : /users/spaces/lefevre/share/zsh/4.0.4/functions
See config.modules for installed modules and functions.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: Problems with modules and zsh 4.0.4

[Phil Pennock]

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

On 2001-10-30 at 14:50 +0100, Vincent Lefevre wrote:
> But when I rlog to this machine, I get errors like:
> 
> /users/spaces/lefevre/.zshrc:54: failed to load module: zsh/rlimits
> /users/spaces/lefevre/.zshrc:limit:54: autoload failed
> /users/spaces/lefevre/.zshrc:104: failed to load module: zsh/parameter
> /users/spaces/lefevre/.zshrc:305: failed to load module: zsh/zle
> /users/spaces/lefevre/.zshrc:bindkey:305: autoload failed
> /users/spaces/lefevre/.zshrc:306: command not found: bindkey
> /users/spaces/lefevre/.zshrc:307: command not found: bindkey
> [...]
> 
> However, if I exec $SHELL after rlogging, I no longer get such
> problems. With zsh 4.0.2, there were no problems at all.

What happens if you add this:
 typeset -m ZSH*
 typeset module_path
before the first autoload?

Ie, what does it show for ZSH_VERSION at that point?  What's the
module_path?

It sounds as though you're trying to load the old versions of the
modules; then, later, the paths are changed and with the exec, the
correct modules can be found.
-- 
I AM THE DEFENDER OF THE SOMETIMES-INEFFICIENT.
FEAR MY CAREFULLY WORDED AND REASONED WRATH.
 - Chris Bellomy

[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]

Re: Problems with modules and zsh 4.0.4

[Vincent Lefevre]

On Tue, Oct 30, 2001 at 15:25:51 +0100, Phil Pennock wrote:
> What happens if you add this:
>  typeset -m ZSH*
>  typeset module_path
> before the first autoload?

I've added this at the beginning of ".zshenv".

> Ie, what does it show for ZSH_VERSION at that point?  What's the
> module_path?

ZSH_NAME=zsh
ZSH=/users/spaces/lefevre/i386-linux/bin/zsh
ZSH_VERSION=4.0.4
module_path=(/users/spaces/lefevre/i686-linux/lib/zsh/4.0.4)

Note that i686-linux is a symlink to i386-linux.

At this point, I get the errors, but if I exec $SHELL as I've said,
I get:

ZSH_NAME=zsh
ZSH=/users/spaces/lefevre/i386-linux/bin/zsh
ZSH_VERSION=4.0.4
module_path=(/users/spaces/lefevre/i686-linux/lib/zsh/4.0.4)

and no errors.

> It sounds as though you're trying to load the old versions of the
> modules; then, later, the paths are changed and with the exec, the
> correct modules can be found.

It doesn't seem to be the problem.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: Problems with modules and zsh 4.0.4

[Vincent Lefevre]

Concerning the difference with zsh 4.0.2, in fact, I think that
I compiled zsh 4.0.2 with gcc 2.95.2. So, I've tried to compile
zsh 4.0.4 with gcc 2.95.2 (instead of 3.0) and I no longer get
the problems. Now, I don't know if these problems come from zsh
or gcc 3.0.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: Problems with modules and zsh 4.0.4

[Vincent Lefevre]

On Tue, Oct 30, 2001 at 18:56:29 +0100, Vincent Lefevre wrote:
> Concerning the difference with zsh 4.0.2, in fact, I think that
> I compiled zsh 4.0.2 with gcc 2.95.2. So, I've tried to compile
> zsh 4.0.4 with gcc 2.95.2 (instead of 3.0) and I no longer get
> the problems. Now, I don't know if these problems come from zsh
> or gcc 3.0.

This comes from LD_LIBRARY_PATH (it was set at the end of .zshenv).

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: Problems with modules and zsh 4.0.4

[Borsenkow Andrej]

On Tue, 30 Oct 2001, Vincent Lefevre wrote:

> Concerning the difference with zsh 4.0.2, in fact, I think that
> I compiled zsh 4.0.2 with gcc 2.95.2. So, I've tried to compile
> zsh 4.0.4 with gcc 2.95.2 (instead of 3.0) and I no longer get
> the problems. Now, I don't know if these problems come from zsh
> or gcc 3.0.
>
>

This comes from GCC (or to be precise, from the particular configuration).
We already had the case. gcc-3 compiled programs need extra shared library
(I forgot the name). If this library could not be found program appears to
work but some things fail.

-andrej