> moo!
> 
> 	okay, so a while back, this problem cropped up by whcih a lot
> 	of programs that had
                         ... bad
> 
> 	extern char *sys_errlist or something like that in them would
> 	start barfing.
> 
> 	what is the 'official' way to solve this?  up until now, i've
> 	been doing it by just commenting these declarations out
> 	as the compiler chokes on them....
> 

Hang these 'programmers'. :-)

sys_errlist is one of the realy rare identifiers with a prefix which
does tell you what it's good for and from where it does come from.
But, of course there have to be always some guys who have to produce
more chaos. I think I found such a 'sys_errlist' declaration i an
emacs source. Well, I've removed emacs from my disk.

> 
> 	is there a more pleasant way to patch this source file stuff?
> 

What's about the following script (call it 'junked', say "junk" "ed"):

#!/bin/sh
for my_file in $*
do
  my_tmp_file=${TMPDIR:=/tmp}/junked.$$.tmp
  mv $my_file $my_tmp_file
  sed 's/\(extern.*\)\(sys_errlist\)/\1bullshit_\2/g' $my_tmp_file > $my_file
  rm -f $my_tmp_file
done

> 
> 
> 							marc 'em.

Henry

--
juengst@saph2.physik.uni-bonn.de   [131.220.221.12]  (internet)
juengst@boss1.physik.uni-bonn.de   [131.220.221.30]
saph2::juengst                     [13.259]          (decnet)

Any opinions in this mail are my own.

------------------------------------------------------------------------------