Add two more patches found in the Linux wild. Would've been

better to be downloading them, but, strangely enough, they
don't seem available in the raw source -- only in the pretty-fied
HTML :-(

Of the two remaining once, the ElectricFence-2.2.2-madvise.patch
is currently causing me unexplained crashes, and the
ElectricFence-2.2.2-pthread.patch does not seem to matter for us,
because we don't USE_SEMAPHORE:

http://www.filewatcher.com/p/ElectricFence-2.2.2-19.src.rpm.38696/ElectricFence-2.2.2-madvise.patch.html
http://www.filewatcher.com/p/ElectricFence-2.2.2-19.src.rpm.38696/ElectricFence-2.2.2-pthread.patch.html

2 files changed, 38 insertions, 0 deletions

diff --git a/devel/ElectricFence/files/patch-longjmp b/devel/ElectricFence/files/patch-longjmp
new file mode 100644
index 000000000000..cafc4c5ef1fa
--- /dev/null
+++ b/devel/ElectricFence/files/patch-longjmp
@@ -0,0 +1,27 @@
+--- eftest.c	Tue Jun  2 09:25:10 1998
++++ eftest.c	Tue Jun  2 09:24:58 1998
+@@ -24,7 +24,7 @@
+ extern int	EF_PROTECT_BELOW;
+ extern int	EF_ALIGNMENT;
+ 
+-static jmp_buf	env;
++static sigjmp_buf	env;
+ 
+ /*
+  * There is still too little standardization of the arguments and return
+@@ -40,13 +40,13 @@
+ )
+  {
+ 	signal(PAGE_PROTECTION_VIOLATED_SIGNAL, SIG_DFL);
+-	longjmp(env, 1);
++	siglongjmp(env, 1);
+ }
+ 
+ static int
+ gotSegmentationFault(int (*test)(void))
+ {
+-	if ( setjmp(env) == 0 ) {
++	if ( sigsetjmp(env, 1) == 0 ) {
+ 		int			status;
+ 
+ 		signal(PAGE_PROTECTION_VIOLATED_SIGNAL
diff --git a/devel/ElectricFence/files/patch-vaarg b/devel/ElectricFence/files/patch-vaarg
new file mode 100644
index 000000000000..a1576d9824ae
--- /dev/null
+++ b/devel/ElectricFence/files/patch-vaarg
@@ -0,0 +1,11 @@
+--- print.c	Thu Jan 19 23:54:26 1995
++++ print.c	Tue May 16 07:43:45 2000
+@@ -99,7 +99,7 @@ vprint(const char * pattern, va_list arg
+ 				break;
+ 			case 'c':
+ 				{
+-					char	c = va_arg(args, char);
++					char	c = va_arg(args, int);
+ 					
+ 					(void) write(2, &c, 1);
+ 				}