-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configure.ac - configure file issue #2
Comments
That's not how you invoke autoconf. Please use boot.sh. |
Thanks for the quick resolution. I am running into another error: configure: error: libopenvswitch.a was not found. Try --with-ovs-libpath I searched for the file in the system but don't find it. I checked the Thanks, On Fri, Mar 13, 2015 at 3:59 PM, Ben Pfaff notifications@github.com wrote:
abhijeet |
Look at https://github.com/openvswitch/of-config/blob/master/INSTALL.md#open-vswitch-installation |
I already have openvswitch running: ovs-vsctl show Just to clarify, I did not build openvswitch from github sources but used This is the output for I looked for libopenvswitch.a and don't find it in the system. On Mon, Mar 16, 2015 at 9:50 AM, Tomas Cejka notifications@github.com
abhijeet |
I was able to install and run ofc-server on RHEL 6.5 after following the Looks like these are unsupported in RHEL6.5 env. If this is right then it Thanks, On Mon, Mar 16, 2015 at 9:50 AM, Tomas Cejka notifications@github.com
abhijeet |
On Mon, Mar 16, 2015 at 03:06:44PM -0700, abhsob wrote:
Probably the correct solution would be to test for these constants and #ifndef ADVERTISED_Pause |
Hi, Dne 16.3.2015 v 18:03 abhsob napsal(a):
good, this is correct (and actually required)
of-config search for it in the ovs-srcdir you set. Maybe it should have a better name or description, because it actually should be the "compiled source codes", not just the "source codes" I expect you have in /root/rpmbuild/SOURCES/openvswitch-2.3.1 - try to use /root/rpmbuild/BUILD/openvswitch-2.3.1instead. Radek
|
hmm, I agree that we should test for these constants, but since we usethese constants when mapping rate from of-config data model from/to ioctl()'s ETHTOOL_GSET and ETHTOOL_SSET calls, we should probably ignore these values if they are not defined in system headers. Or do you think that the driver can define and use these rates on its own without support in the system headers, so we can get/set such values via ioctl()? Radek Dne 16.3.2015 v 23:13 Ben Pfaff napsal(a):
|
On Tue, Mar 17, 2015 at 12:28:31AM -0700, Radek Krejčí wrote:
The machine on which the code builds is not necessarily the machine on |
Hi Radek, I used the instructions in using the distribution tarball. In that case, I don't see Then I deployed the openvswitch on another VM and did configure, make and Thanks, On Tue, Mar 17, 2015 at 12:17 AM, Radek Krejčí notifications@github.com
abhijeet |
same as @abhsob on Ubuntu 16.10 and OVS 2.7 .. checking for library containing ovsrec_init... no $ sudo find / -iname libopenvswitch.a -type f any updates? |
Even I am facing same problem with debian jessie and OVS 2.9.2. OF-config and OVS were taken from source. |
|
If you are still getting "error: possibly undefined macro: LT_INIT" you need to install libtool. |
I see the following issue when generating configure file. RHEL 6.5. Can these be ignored?
autoconf configure.ac > configure
configure.ac:8: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:21: error: possibly undefined macro: AM_PROG_CC_C_O
configure.ac:25: error: possibly undefined macro: AC_MSG_ERROR
configure.ac:27: error: possibly undefined macro: AC_DEFINE_DIR
configure.ac:29: error: possibly undefined macro: LT_INIT
configure.ac:51: error: possibly undefined macro: AM_CONDITION
The configure file is generated so I tried to execute it. On running the configure see the following issue related to AM_INIT_AUTOMAKE
/configure: line 1819: syntax error near unexpected token
foreign' ./configure: line 1819:
AM_INIT_AUTOMAKE(foreign subdir-objects)'The text was updated successfully, but these errors were encountered: