4.0.9

4.0.9

[Peter Stephenson]

I've uploaded 4.0.9.  The only difference from 4.0.8 was to add the
missing mod_export declarations, for dynamic loading on systems that
need to be told what to export, so if you've already installed 4.0.8
there's no benefit in getting 4.0.9.  (The FTP site is still tidying
itself up but the main files are there.)

It's also now on Sourceforge and recorded at Freshmeat.

As per tradition, I will be away for two weeks after this evening.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: 4.0.9

[Carlos Carvalho]

Module loading doesn't work for me in either 4.0.8 or 4.0.9. I'm using
gcc 3.3.2 and the latest libc from debian unstable. I used this
configuration:

% ./configure  --prefix=/usr --bindir=/bin --mandir=/usr/share/man --infodir=/usr/share/info --enable-maildir-support --enable-max-jobtable-size=256 --enable-function-subdirs --enable-site-fndir=/usr/local/share/zsh/site-functions --with-curses-terminfo --enable-etcdir=/etc/zsh

and get:

% Src/zsh
/etc/zsh/zshenv:9: failed to load module: zsh/rlimits
/etc/zsh/zshenv:ulimit:9: autoload failed
/etc/zsh/zshrc:24: failed to load module: zsh/zle
/etc/zsh/zshrc:bindkey:24: autoload failed
/etc/zsh/zshrc:26: failed to load module: zsh/zle
...
and it ends up segfaulting.

Re: 4.0.9

[DervishD]

    Hi Carlos :)

 * Carlos Carvalho <carlos@fisica.ufpr.br> dixit:
> Module loading doesn't work for me in either 4.0.8 or 4.0.9. I'm using
> gcc 3.3.2 and the latest libc from debian unstable.

    I've tested with 4.0.9, GCC 3.3, libc 2.2.4, and have the same
problem.

> and it ends up segfaulting.

    Mine didn't segfaulted, but it was unable to load modules.
Anyway, I've done a quick and dirty test, so I'm not sure if the
problem is my fault (which is, probably).

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: 4.0.9

[Wayne Davison]

On Sat, Dec 20, 2003 at 06:51:15PM -0200, Carlos Carvalho wrote:
> % Src/zsh
> /etc/zsh/zshenv:9: failed to load module: zsh/rlimits [...]

Did you install the libraries via "make install" first?  If not, try
"make test" (instead of Src/zsh) and see if that works.

..wayne..

Re: 4.0.9

[Carlos Carvalho]

DervishD (raul@pleyades.net) wrote on 21 December 2003 14:08:
 > * Carlos Carvalho <carlos@fisica.ufpr.br> dixit:
 >> Module loading doesn't work for me in either 4.0.8 or 4.0.9. I'm using
 >> gcc 3.3.2 and the latest libc from debian unstable.
 >
 >    I've tested with 4.0.9, GCC 3.3, libc 2.2.4, and have the same
 >problem.
 >
 >> and it ends up segfaulting.
 >
 >    Mine didn't segfaulted, but it was unable to load modules.
 >Anyway, I've done a quick and dirty test, so I'm not sure if the
 >problem is my fault (which is, probably).

I found that the module loading didn't work because the installation
process didn't complete and the modules were not put in the system
area.

The segfaulting is happening with several other programs in an
apparently random fashion; rebooting "cures" it for a while. Therefore
it's not zsh-related. Looks like some cache mis-behavior...

Sorry for the false alarm.

Re: 4.0.9

[DervishD]

    Hi Carlos :)

 * Carlos Carvalho <carlos@fisica.ufpr.br> dixit:
>  >> and it ends up segfaulting.
>  >    Mine didn't segfaulted, but it was unable to load modules.
>  >Anyway, I've done a quick and dirty test, so I'm not sure if the
>  >problem is my fault (which is, probably).
> I found that the module loading didn't work because the installation
> process didn't complete and the modules were not put in the system
> area.

    In my system the installation seemed to complete :?? I didn't
tested if modules were installed, but 'make install' is supposed to
do it, am I wrong?

    Anyway, it can be an issue with my current RC files. Not a
problem ;))
 
    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: 4.0.9

[Carlos Carvalho]

Wayne Davison (wayned@users.sourceforge.net) wrote on 21 December 2003 07:13:
 >try "make test" (instead of Src/zsh) and see if that works.

Nice. Everything works until

./Y01completion.ztst: starting.
comptestinit:zpty:19: can't open pseudo terminal: bad file descriptor
comptestinit:zpty:21: no such pty command: zsh

Compiling and running on another machine works so it's not a zsh problem.

Re: 4.0.9

[DervishD]

    Hi Carlos :)

 * Carlos Carvalho <carlos@fisica.ufpr.br> dixit:
> ./Y01completion.ztst: starting.
> comptestinit:zpty:19: can't open pseudo terminal: bad file descriptor
> comptestinit:zpty:21: no such pty command: zsh

    I've notified an almost-a-bug related to that issue. Maybe you're
running a Linux box that has support for ptmx and doesn't have
/dev/pty?? nodes. If that is true, then zsh pty subsystem won't work
for you. You will need to create the /dev/pty?? nodes, since zsh
thinks that Linux doesn't support ptmx. Not a problem, really.

    This may be fixed in the 4.1.x series.
 
    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: 4.0.9

[Carlos Carvalho]

DervishD (raul@pleyades.net) wrote on 21 December 2003 18:50:
 > * Carlos Carvalho <carlos@fisica.ufpr.br> dixit:
 >> ./Y01completion.ztst: starting.
 >> comptestinit:zpty:19: can't open pseudo terminal: bad file descriptor
 >> comptestinit:zpty:21: no such pty command: zsh
 >
 >    I've notified an almost-a-bug related to that issue. Maybe you're
 >running a Linux box that has support for ptmx and doesn't have
 >/dev/pty?? nodes. If that is true, then zsh pty subsystem won't work
 >for you. You will need to create the /dev/pty?? nodes, since zsh
 >thinks that Linux doesn't support ptmx. Not a problem, really.

On the box where the test fails:

hoggar% ls /dev/pty*
/dev/ptyp0  /dev/ptyp3  /dev/ptyp6  /dev/ptyp9  /dev/ptypc  /dev/ptypf
/dev/ptyp1  /dev/ptyp4  /dev/ptyp7  /dev/ptypa  /dev/ptypd
/dev/ptyp2  /dev/ptyp5  /dev/ptyp8  /dev/ptypb  /dev/ptype

It also has /dev/ptmx. The box where the tests pass uses devfs; it has
all the pty's from a0 to zf, they're symlinks to /dev/pty/m*, and no ptmx.

Is this a problem with the configuration?

Re: 4.0.9

[DervishD]

    Hi Carlos :)

 * Carlos Carvalho <carlos@fisica.ufpr.br> dixit:
>  >    I've notified an almost-a-bug related to that issue. Maybe you're
>  >running a Linux box that has support for ptmx and doesn't have
>  >/dev/pty?? nodes. If that is true, then zsh pty subsystem won't work
>  >for you. You will need to create the /dev/pty?? nodes, since zsh
>  >thinks that Linux doesn't support ptmx. Not a problem, really.
> On the box where the test fails:
> hoggar% ls /dev/pty*
> /dev/ptyp0  /dev/ptyp3  /dev/ptyp6  /dev/ptyp9  /dev/ptypc  /dev/ptypf
> /dev/ptyp1  /dev/ptyp4  /dev/ptyp7  /dev/ptypa  /dev/ptypd
> /dev/ptyp2  /dev/ptyp5  /dev/ptyp8  /dev/ptypb  /dev/ptype

    Certainly is not a problem with the PTY nodes...
 
> It also has /dev/ptmx. The box where the tests pass uses devfs; it has
> all the pty's from a0 to zf, they're symlinks to /dev/pty/m*, and no ptmx.
> Is this a problem with the configuration?

    Don't think so. Try 'strace' and see if opening the PTY gives a
sensible error or the like. 

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/