At 07:46 PM 12/5/2001 +, Nick Burch wrote:
> >Since 0.0.3 is exceptionally imminent, can I have a roll-call of systems
> >which are working and not working?
>
>OS/2 + EMX Working
>
>Tinderbox + internal lan with private dns + os/2 sendmail broke,
>hence its not in the tinder
>Since 0.0.3 is exceptionally imminent, can I have a roll-call of systems
>which are working and not working?
OS/2 + EMX Working
Tinderbox + internal lan with private dns + os/2 sendmail broke,
hence its not in the tinderbox...
Nick
Oh, you technical people:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>FreeBSD 4.4 / gcc
>>Irix6.5 / MIPSPro
>Would those be working or not working? :)
The answer is, obviously, "Yes."
Now get back to work.
Whoops--that was someone talking to me!
John A
On Wed, 5 Dec 2001, Simon Cozens wrote:
> I've finally got around to adding perlundef.pmc, which means that the
> classes/Makefile has changed; this means you'll all - and tinderbox people
> especially - have to rerun Configure. I suppose someone should add tests
> for perlundef.pmc, but I hate w
At 05:57 PM 12/5/2001 +, Alex Gough wrote:
>On Wed, 5 Dec 2001, Simon Cozens wrote:
>
> > Since 0.0.3 is exceptionally imminent, can I have a roll-call of systems
> > which are working and not working?
>
>FreeBSD 4.4 / gcc
>Irix6.5 / MIPSPro
Would those be working or not working? :)
At 05:42 PM 12/5/2001 +, Simon Cozens wrote:
>and tinderbox people
>especially - have to rerun Configure.
Doing a "make clean" looks to be required first to get tinderbox checkouts
happy again.
Dan
--"it's like thi
On Wed, 5 Dec 2001, Simon Cozens wrote:
> Since 0.0.3 is exceptionally imminent, can I have a roll-call of systems
> which are working and not working?
FreeBSD 4.4 / gcc
Irix6.5 / MIPSPro
Alex
