Hello Robert Watson,

From: Robert Watson <[EMAIL PROTECTED]>
Date: Sun, 16 Jun 2002 02:44:18 -0400 (EDT)
::> 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. 

I realized that my world was not in sync, just after I send out my e-mail.
Thank you for feed back, anyway. :-)

I hope my original e-mail would be a small heads-up for the rest of
zsh users, who may get into same kind of trouble. :-P

           _ _    Munehiro (haro) Matsuda
 -|- /_\  |_|_|   Business Incubation Dept., Kubota Corp.
 /|\ |_|  |_|_|   1-3 Nihonbashi-Muromachi 3-Chome
                  Chuo-ku Tokyo 103-8310, Japan
                  Tel: +81-3-3245-3318  Fax: +81-3-3245-3315
                  Email: [EMAIL PROTECTED]

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

Reply via email to