On 05/01/2011 10:20 PM, James Mansion wrote:
OK I have it working now. I thought that having it working on my
portable dev system meant that I'd done something screwy on the server
and retrying would work, but it was not to be.
First detail - for anyone who imports the sources into other build
systems or IDEs: if you get this sort of thing in the crypt for
passwords and the authentication fails, its because you don't have
-funsigned-char.
Is this where I rant about how char should have been unsigned? When was
the last time you saw a human say things like "รค is codepoint -32 in
latin1" instead of 224? (The pedants may point out that the codepoint is
wrong anyway.) That the compiler disagrees with how humans describe
chars among themselves is a fscking language bug, I say.
It turns out that lib/installer was failing trying to add an index -
(which?)
I added user aoxsuper, temporarily made the aoxsuper.conf and
archiveopteryx.conf readable by aoxsuper, and ran 'bin/aox upgrade
schema' as aoxsuper - which worked like a charm. I had to reset the
readability before I could start aox, or course.
One annoyance is that while I could run 'aox upgrade schema' as
aoxsuper, I could not run 'aox show schema' as aoxsuper - it wants to
connect as aox.
Its working now but this was a bit messy. Maybe I'll try a thunderbird
upgrade when I feel better about it. ;-)
A bit messy, sure. Sorry about that.
I think the main concern I have is that there isn't a
'--be-very-verbose' option in aox that would print out what was going
on, sort of thing I'd turn on in systems like log4cxx and the like.
Patches would be welcome. I agree that such an option would be fine, but
the concrete diff is a long distance away... I've already spend a couple
of days one time trying to do that and ended up not knowing what exactly
should be printed. --be-very-verbose is more or less the same as
--describe-the-bug, and that's difficult in advance ;)
Still concerned that the 'warnings as errors' is OK with the gcc on my
server (4.2.4) but not on the VM I use while commuting (4.4.1) - both
with whatever patches Ubuntu decided to use. 4.4.1 is hardly news, is it
really that no-one using a recent gcc is building with Jam? Implies that
no-ones's doing dev on those systems, because the Makefile is just a
linear script. :-(
No, it's that we released 3.1.3 just before gcc started doing those
(stupid) warnings, and still haven't gotten 3.1.4 out the door. For
which there are good reasons, but a) it's been long enough and b) we've
solved the trickiest of the problems anyway, rejoice.
Arnmt
