fuzzball compile time error

22 views
Skip to first unread message

Yue Duan

unread,
Jun 10, 2015, 6:47:23 PM6/10/15
to bitblaz...@googlegroups.com
Hi all,

I followed exactly the same step as INSTALL file in fuzzball directory. But I dont quite understand this command "./configure --with-vex=<...> ...". So I just assume it is "./configure --with-vex=/path/to/vex-r2737"

But when I "make" fuzzball, it shows

The working copy at 'xx/vex-r2737'
is too old (format 29) to work with client version '1.8.8 (r1568071)' (expects format 31). You need to upgrade the working copy first.


Looks like it is complaining about the version of vex, but i am using the version 2737 suggested by the INSTALL file. What version of vex should I use to compile?

Thanks,
Yue

Stephen McCamant

unread,
Jun 12, 2015, 5:09:42 PM6/12/15
to bitblaz...@googlegroups.com
>>>>> "YD" == Yue Duan <bestd...@gmail.com> writes:

YD> Hi all,
YD> I followed exactly the same step as INSTALL file in fuzzball
YD> directory. But I dont quite understand this command "./configure
YD> --with-vex=<...> ...". So I just assume it is "./configure
YD> --with-vex=/path/to/vex-r2737"

Yes, that's what was intended.

YD> But when I "make" fuzzball, it shows

YD> The working copy at 'xx/vex-r2737'
YD> is too old (format 29) to work with client version '1.8.8 (r1568071)'
YD> (expects format 31). You need to upgrade the working copy first.

YD> Looks like it is complaining about the version of vex, but i am
YD> using the version 2737 suggested by the INSTALL file. What version
YD> of vex should I use to compile?

I think if you look at the version numbers in the error message, they
aren't right to be version numbers of VEX. "r1568071" is an SVN-style
revision number, but it's much too large to be for VEX.

Rather I think this error message is coming from SVN: the compilation
process uses "svn info", among other techniques, to try to determine
what version of VEX you've supplied, since different versions of VEX
are slightly incompatible. This error message (which you can find
plenty more discussion of if you search the web) indicates that you
checked out the directory using an older and incompatible version of
SVN compared to the version running the "svn info" command. This might
happen if you check out on one computer and copy the directory to
another computer (or via NFS, etc.), or if you upgraded your version
of SVN, etc. If you can easily just remove the directory and check it
out again with your current SVN client version, that might be the
cleanest fix. The "upgrade" process the error message refers to is
"svn upgrade", which should be available in your newer SVN
client. More general SVN documentation of this issue is at:

http://subversion.apache.org/docs/release-notes/1.8.html#wc-upgrade

For the FuzzBALL version of this issue in particular, you should also
be able to avoid the need to run "svn info" by manually supplying the
option --with-vex-revision=2737 to FuzzBALL's configure script.

Hope this helps,

-- Stephen
Reply all
Reply to author
Forward
0 new messages