[Openmcl-devel] Latest trunk (r13464) build issue??

Jon S. Anthony j-anthony at comcast.net
Fri Feb 26 23:54:37 UTC 2010

On Fri, 2010-02-26 at 14:32 -0700, Gary Byers wrote:

> I think of this as being pretty clearly spelled out (at least in those
> Wiki pages), but enough people are surprised often enough that this must
> not be as clear as I think it is. 

I'm guessing it's because those pages weren't read or read as closely as
they should be. :-|

> Although it's been successful in that regard, this new policy has frankly
> not made me nearly as rich as I'd hoped it would; I'd hoped to be able
> to retire to a fairly large private island by now, and all I've gotten
> out of it is a lousy IOU.  Obviously, people using the trunk need some
> sort of reminder of the fact that trunk binaries aren't kept up to date
> and that this may lead to benign warnings and (until we can suppress them)
> occasional CERRORs on constant redefinition, and I think that the same
> scheme might be expected to have a similar deterrent effect.
> So, I'd be glad if people who use the trunk were aware of the issue and
> stopped reporting expected behavior.  I'd be equally glad (for different
> reasons) if 30 or so people forgot and reported "dog bites man!", as long
> as those people pay promptly and in cash.

Well, I typically don't use the trunk (which, or course, causes other
problems).  Still, I appreciate your frustration and I'll take you up on
your suggested new policy for this sort of thing.  Where do you want me
to send you your $1.00.  You can send the info in private email.


More information about the Openmcl-devel mailing list