Fix the spelling of longjmp in pex-unix.c

[Matt Kraai]

Howdy,

I committed the following patch as obvious.

-- 
Matt

Index: libiberty/ChangeLog
===================================================================
RCS file: /cvs/gcc/gcc/libiberty/ChangeLog,v
retrieving revision 1.533
diff -u -c -3 -p -r1.533 ChangeLog
*** libiberty/ChangeLog	24 Nov 2004 02:19:09 -0000	1.533
--- libiberty/ChangeLog	30 Nov 2004 02:53:22 -0000
***************
*** 1,3 ****
--- 1,7 ----
+ 2004-11-29  Matt Kraai  <kraai@alumni.cmu.edu>
+ 
+ 	* pex-unix.c: Fix the spelling of longjmp.
+ 
  2004-11-23  Ian Lance Taylor  <ian@wasabisystems.com>
  
  	PR other/18623
Index: libiberty/pex-unix.c
===================================================================
RCS file: /cvs/gcc/gcc/libiberty/pex-unix.c,v
retrieving revision 1.2
diff -u -c -3 -p -r1.2 pex-unix.c
*** libiberty/pex-unix.c	18 Mar 2004 03:16:37 -0000	1.2
--- libiberty/pex-unix.c	30 Nov 2004 02:53:22 -0000
*************** extern int errno;
*** 61,67 ****
     via other calls to this function.
  
     This version of the function uses vfork.  In general vfork is
!    similar to setjmp/longmp, in that any variable which is modified by
     the child process has an indeterminate value in the parent process.
     We follow a safe approach here by not modifying any variables at
     all in the child process (with the possible exception of variables
--- 61,67 ----
     via other calls to this function.
  
     This version of the function uses vfork.  In general vfork is
!    similar to setjmp/longjmp, in that any variable which is modified by
     the child process has an indeterminate value in the parent process.
     We follow a safe approach here by not modifying any variables at
     all in the child process (with the possible exception of variables