Discussion:
[qpimd-users] config.h.in patch
Andrew Lunn
2009-04-15 07:29:03 UTC
Permalink
Hi Folks

In order to get qpimd to compile i had to patch config.h.in. Without
these changes, configure would correctly determine things, but they
never made it to config.h.

Andrew

--- quagga-0.99.11/config.h.in 2008-10-02 10:31:32.000000000 +0200
+++ quagga/config.h.in 2009-04-14 15:20:58.000000000 +0200
@@ -570,6 +570,9 @@
/* ospfd vty socket */
#undef OSPF_VTYSH_PATH

+/* pimd vtu socket */
+#undef PIM_VTYSH_PATH
+
/* Name of package */
#undef PACKAGE

@@ -615,6 +618,9 @@
/* zebra PID */
#undef PATH_ZEBRA_PID

+/* pimd PID */
+#undef PATH_PIMD_PID
+
/* Quagga Group */
#undef QUAGGA_GROUP

@@ -746,3 +752,9 @@
/* Define to empty if the keyword `volatile' does not work. Warning: valid
code using `volatile' can become incorrect without. Disable with care. */
#undef volatile
+
+/* Define to 1 if you have the IP_PKTINFO setsockopt */
+#undef HAVE_IP_PKTINFO
+
+/* Define to 1 if you have the IP_RECVDSTADDR setsockopt */
+#undef HAVE_IP_RECVDSTADDR
Everton Marques
2009-04-15 10:40:13 UTC
Permalink
Hi,
Post by Andrew Lunn
In order to get qpimd to compile i had to patch config.h.in. Without
these changes, configure would correctly determine things, but they
never made it to config.h.
I just checked that my local config.h.in has those same definitions.

I see this comment at the top of config.h.in:
/* config.h.in. Generated from configure.ac by autoheader. */

So I am guessing that config.h.in is supposed to be generated by autotools.

For reference, I build qpimd in my local development repository by
running the following script: ./pimd/quagga-build.sh
This script calls quagga's bootstrap.sh to issue the autotools-generated files.

I think the changes you proposed for config.h.in should be included in a
release to enable qpimd to be built in systems lacking autotools?

Cheers,
Everton

Loading...