On Wed, Jun 18, 2014 at 6:38 PM, lin shaopeng <slin0...@gmail.com> wrote:

> Hi, everyone
>
> I am experiencing some strange error of my ovs build.  I tried google, but
> none of the answer provided can fix this issue.  Anyone have the similar
> problem can give
> me a hint, how to solve it or how to troubleshooting it? Thank you very
> much!
>
> The following is the error message I got when compiling ovs 2.0.1.
>
> ----------------------------------------------------------------------------
> chmod +x utilities/bugtool/ovs-bugtool.tmp
> mv utilities/bugtool/ovs-bugtool.tmp utilities/bugtool/ovs-bugtool
> printf '\043 Generated automatically -- do not modify!    -*-
> buffer-read-only: t -*-\n' > version.py.tmp
> echo 'VERSION = "2.0.1"' >> version.py.tmp
> if cmp -s version.py.tmp python/ovs/version.py; then touch
> python/ovs/version.py; rm version.py.tmp; else mv version.py.tmp
> python/ovs/version.py; fi
> /bin/sh /data/panlin/ovs-2.0.1-0618/openvswitch-2.0.1/build-aux/missing
> --run autom4te --language=autotest -I '.' -o tests/testsuite.tmp tests/
> testsuite.at
> /usr/bin/m4:tests/ofp-print.at:454: recursion limit of 1024 exceeded, use
> -L<N> to change it
> autom4te: /usr/bin/m4 failed with exit status: 1
> make[2]: *** [tests/testsuite] Error 1
> make[2]: Leaving directory `/data/panlin/ovs-2.0.1-0618/openvswitch-2.0.1'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/data/panlin/ovs-2.0.1-0618/openvswitch-2.0.1'
> make: *** [all] Error 2
>

I have overcome this issue with my autoconf updated from 2.63 to 2.69.
But still not clear what exactly the cause of the issue, it seems there is
a bug in tests/ofp-print.at:454,
there is an extra ")" after word "data", see below
------------------------------------------------------------------------------------------------------------
 454 AT_SETUP([OFPT_PACKET_IN - OF1.0, with hex output of packet data)])
 455 AT_KEYWORDS([ofp-print])
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to