Re: Bug#151886: status of report #151886? / feedback

2002-12-29 Thread Matthias Klose
Camm Maguire writes:
 Greetings!
 
 Matthias Klose [EMAIL PROTECTED] writes:
 
  [keeping all the people in the CC]
  
  Scanning the reports, I see Matthew Wilcox beeing asked about:
  
In either case, I will need a knowledgeable hppa person to advise,
discuss and help generate patches for this to get fixed any time soon.
Gcl can build its own bfd library, so patches here can be simply
incorporated.
   
   willy would be a good target.  I'm going to be out of town for a couple
   of weeks, but (if it's still pending) I'd be happy to help when I get
   back.
  
  Camm, another try with the current (20021227) gcc-snapshot package
  (now branched to become gcc-3.3 sometime).
  
  
 
 I forget which of the several gcc difficulties I'd been having with
 GCL on hppa to which this note referred.

yes, the report got long ...

 In any case, I see I'm going to have a problem with 3.3:
 
 /home/camm/usr/lib/gcc-snapshot/lib/gcc-lib/hppa-linux/3.3/include/varargs.h:4:2:
  #error GCC no longer implements varargs.h.
 /home/camm/usr/lib/gcc-snapshot/lib/gcc-lib/hppa-linux/3.3/include/varargs.h:5:2:
  #error Revise your code to use stdarg.h.
 
 Fixing this will take considerable effort.  Is there a work around to
 get varargs under 3.3?

I don't think so:

2002-07-15  Zack Weinberg  [EMAIL PROTECTED]

* ginclude/varargs.h: Replace with stub which issues #error.
* ginclude/stdarg.h: __builtin_stdarg_start is renamed
__builtin_va_start.

[...]

* doc/invoke.texi, doc/sourcebuild.texi, doc/tm.texi,
doc/trouble.texi: Remove references to GCC-provided varargs.h.




howto disable A500's temperature cut-out safety feature?

2002-12-29 Thread James Troup
Hi,

sarti.d.o (an A500) is hosted in a room whose AC unit is having issues
atm and occasionally it switches itself off until it gets some
attention from a human.  Of all the machines in there, only sarti
notices the resulting excessive temperature and switches itself off (I
assume?).  The problem is, once it does this, the only way to restore
it is to physically (and on-site) power cycle it, the GSP doesn't
work, 'RS' just whines that SPU power is down!.  'PC' doesn't work
either, saying The system did not respond to the Power-On command.

Is there anyway to work around this?

-- 
James

P.S. I am aware that the correct solution is to just fix the AC, but
 that's out of my hands.