On Sun, 16 Jun 2002, Munehiro Matsuda wrote:

> Hello Robert Watson,
> After removal of cap_get_proc() and friends from libc, zsh from the ports
> started to dump core:
> <snip>
> #0  0x28172333 in __sys___cap_get_proc () from /usr/lib/libc.so.5
> (gdb) where
> #0  0x28172333 in __sys___cap_get_proc () from /usr/lib/libc.so.5
> #1  0x2816003e in cap_get_proc () from /usr/lib/libc.so.5
> #2  0x280ca331 in privasserted () from /usr/local/lib/zsh/libzsh-4.0.4.so
> #3  0x28080099 in evalcond () from /usr/local/lib/zsh/libzsh-4.0.4.so
> #4  0x2807e5d7 in bin_test () from /usr/local/lib/zsh/libzsh-4.0.4.so
> <snip> 
> I had to manually disable HAVE_CAP_GET_PROC in config.h for zsh.
> Can't we have some kind of HEADS-UP or version-bump for this matter. 

__cap_get_proc() has always returned ENOSYS in the base system (indicating
that it was not implemented), as we never committed the implementation of
the system call.  It looks like your binary is picking up cap_get_proc() 
from libc, which suggests your libc isn't in sync with the source tree,
since libc no longer contains cap_get_proc().  It may be that zsh's
autoconf picked up on the library calls (now removed), and built in a
dependency on them.  You might need to rebuild zsh to work around this
once libc is rebuilt. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]      Network Associates Laboratories

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to