Build after svn update seems to fail about shellinabox HOT 2 CLOSED

Can you check whether 'svn st' shows any files as having conflicts? That would
certainly explain this behavior.

Most likely, you will need to either delete the conflicting files from your 
system
and then get them again from SVN. Or, alternatively, you could do what the error
message tells you. Delete 'aclocal.m4' and run 'libtoolize' and 'autoreconf'.

I have just submitted a change to SVN that might fix this issue in the future. 
But I
am not 100% sure it will.

Things are optimized for users who either download the tar balls, or who do a 
fresh
checkout from SVN, and who do not want to know about the details of using 
autotools.
This would be the majority of my users.

Unfortunately, this puts those users at a small disadvantage, who like you want 
to
track development with 'svn update'. You might have to actually learn about how 
to
use autotools (or use the exact same version that I use).

I am trying to strike a reasonable compromise here, but it is hard to 
accommodate
these too very different use cases. Let me know, if the new change in SVN makes
things better going forward.

Alternatively, I could check in a script that you could run instead of running 
'svn
update'. Maybe, that's a reasonable approach?

I now added an "update" script. Try running that instead of running "svn 
update".