Subject: misc/6520: setjmp.h handles renaming a little differently from everything else
To: None <gnats-bugs@gnats.netbsd.org>
From: TheMan <andrew@untraceable.net>
List: netbsd-bugs
Date: 12/01/1998 18:20:15
>Number:         6520
>Category:       misc
>Synopsis:       setjmp.h handles renaming a little differently from everything else
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Dec  1 15:35:00 1998
>Last-Modified:
>Originator:     TheMan
>Organization:
none really...
>Release:        current
>Environment:
System: NetBSD noc 1.2 NetBSD 1.2 (null) #4: Fri Oct 24 01:27:28 EDT 1997 root@noc:/usr/src/sys/arch/i386/compile/null i386
yeah yeah yeah...i need to upgrade.

>Description:

whilst fighting (at home) with an upgrade via source, i found this.
it's not really a problem, but it's different from the other places
where functions are being renamed.

>How-To-Repeat:

read sys/stat.h
read signal.h
read setjmp.h
decide that setjmp.h is the odd one out and wants to change.

>Fix:

--- setjmp.h.orig       Mon Sep 14 08:07:31 1998
+++ setjmp.h    Mon Nov  9 10:36:11 1998
@@ -56,7 +56,7 @@
 #include <sys/cdefs.h>
 
 __BEGIN_DECLS
-#if defined(__LIBC12_SOURCE__)
+#ifdef __LIBC12_SOURCE__
 int    __setjmp14 __P((jmp_buf));
 void   __longjmp14 __P((jmp_buf, int));
 

>Audit-Trail:
>Unformatted: