🚀 go-pugleaf

In one of my pleas for help, I wrote about the problem I had below on
a MIPS RISCos5.01 machine.  Wouldn't you know it that shortly after I
posted the article (and couldn't CANCEL it, argh!), I realized that
the ______EBEB_ file is the table of contents generated by ar.  'ar x'
also extracts this file and gives it permissions of 000, so the second
'ar x' in the tmpcopy directory failes...  Maybe an 'rm -f *____EBEB_'
command in this section of the makefile might be appropriate to get
rid of the error message!

In article <gwolskCA8B1x.57s@netcom.com> gwolsk@netcom.com (Guntram Wolski) writes:


   While attempting an install of gcc-2.4.5 on MIPS RISCos 5.01
   with the 'configure mips-mips-riscos5bsd' files I had some
   problems.  The first one being simple to resolve, fixinc.mips
   was not distributed as executable (mode was 666).  To be
   changed in distribution tar file?


   The final problem seems to be a non-problem, but maybe could be fixed
   or documented.  Appropriate output:
	   mv tmplibgcc2.a libgcc2.a
	   rm -rf tmplibgcc.a libgcc.a tmpcopy
	   mkdir tmpcopy
	   if [ xlibgcc1.null != x ];                      \
	   then (cd tmpcopy; ar x ../libgcc1.null);        \
	   else true;                                      \
	   fi
	   (cd tmpcopy; ar x ../libgcc2.a)
   ar: Error: __________EBEB_ cannot create
	   (cd tmpcopy; ar rc ../tmplibgcc.a *.o)
	   rm -rf tmpcopy

   The ar: Error is a bit "scary" to a person installing this for
   the first time.  I haven't researched this completely, but
   if anyone has any insight, thoughts are appreciated.

   Thanks,
   Guntram Wolski
   gwolsk@netcom.com