Changes in config.param between 2.0.0 and 2.0.1

Hi all, I recently downloaded NGPT 2.0.1, configured it and was surprised to 
find that it wouldn't compile. After a bit of digging around I noticed that 
during the configuration process, 2.0.1 was making the decision

decision on mctx implementation... mcsc/sc/mc

whereas 2.0.0 behaved differently, giving

decision on mctx implementation... sjlj/ssjlj/sas

BTW, this is all on a pretty much stock SuSE 7.2 system, with the only 
significany difference being a 2.4.19 kernel with the patches required by 
NGPT applied. The configure script identifies the system as

Platform: i686-suse-linux-gnu2.4glibc2.2

Further digging turned up the fact that the config.param file changed between 
2.0.0 and 2.0.1. The differences are...

--- ngpt-2.0.0/config.param     Wed Jun 26 22:03:12 2002
+++ ngpt-2.0.1/config.param     Thu Aug  1 23:09:47 2002
@@ -32,9 +32,9 @@
     --enable-pthread
     --enable-maintainer
     --enable-syscall-hard
-    --with-mctx-mth=sjlj
-    --with-mctx-dsp=ssjlj
-    --with-mctx-stk=sas
+    --with-mctx-mth=mcsc
+    --with-mctx-dsp=sc
+    --with-mctx-stk=mc
 #   --enable-thread_db
 }

Now I don't know precisely what this file is for, but this difference 
*definitely* made me suspicious. So I commented out all of the lines relating 
to mctx, then ran configure. Voila! 2.0.1 compiled without error! Presumably 
commenting out those lines ensures that configure actually trusts the results 
of its tests and so chooses the correct mctx implementation.

So unless I'm missing something here, and those "mctx" lines really are 
important, I'd suggest removing them!

Regards
M.Beach