🚀 go-pugleaf

> He thought it was uploaded - there may be some sort of
> bottleneck at SOME point...  Archive maintainers should maybe take a
> look around and see if GCC 2.0 is maybe hiding in a subdirectory
> somewhere!

Perhaps this is my fault for not publicly announcing my withdrawal from
assisting the administration of A.A's gnustuff. Over the last 12 months I have
tried to rationalise the gnustuff archives and bring them up to date. By and
large this has been done.

The amount of effort required to maintain the currency of the s/w is beyond me
and I dropped out of the loop several months ago. Since then, the only GNU s/w
which has been added to A.A. is that which other folks have u/ld.

I have a long-standing request from a fellow Brit for the GCC suite on cart
tape, so I decided to update my copy of GCC when 2.0 came out. I d/led the s/w
from A.A., applied ++jrb's updates (14->19) and compiled up the binaries with
an HP-hosted cross-compiler. I've been doing this at my own speed during
lunchtimes and it's very little additional effort to package up the updated
sources and resultant binaries and u/l them to A.A., hence my recent posting on
the subject. *But* that's as far as I intend to take it. 

I hoped to u/l some of it this week but I had to fly to Stuttgart on Monday,
spent Tuesday in Stuttgart, am writing the trip report today, have all Thursday
a.m. scheduled for a meeting, Thursday p.m. for urgent admin work (expenses
from Stuttgart, etc) and on Friday will need to get on with deadlined project
write-ups.  As you can see, there's little time left for pratting about with
trivialities such as s/w for my home computer. Hence the delay chaps, sorry and
all that but ... I'll see what I can do during lunchtimes. 

Cheers,

--
Graham Higgins 					gjh@hpl.hp.com (okay Michael?)
<< My opinions above are exactly that: my own, and opinions. >>