Yes, I'll make a note to bisect the problem. I feel like I'd like to get a release out sooner rather than later, so I might be inclined to let it slide this time around, but then work on getting a new stable release in the next 3 months. I think it's important to get something out, even if it's got some minor issues, as it helps me feel like I've accomplished something, and lets others know that wheels are turning, however slowly.
Re: Win builds, thanks for the more detailed info, I must have missed it the first time around. I've got a fair amount of this sorted out myself, but it's good to get confirmation. I'll make a note of consolidating it with my own and put them someplace public.
Bill
On Tue, 3 Jul 2012, Martin Stjernholm wrote:
Bill Welliver bill@welliver.org wrote:
Well, mine fails 2 tests in Calendar, but I think it's been doing that for some time:
Yes, I get those too. The fact that they're old doesn't make them any less buggy, imo. A way to help sort it out could be to bisect out the responsible commit.
I also got more errors due to that putenv() seemingly didn't work, but they disappeared now when I started digging. :\ Strange, but I guess they can be written off as observational errors then.
Out of curoisity, what does your windows build environment look like? (OS, compiler, etc)...
sprshd, Windows Vista, Visual Studio 2005, GnuWin32 stuff, and various libraries taken from the net. Everything is quite old by now, but it still works. I wrote a longer explanation how it's set up on the other pike list a while ago. Here's a link in case you missed it: article.gmane.org/gmane.comp.lang.pike.user/8287