Source: openfortivpn
Version: 1.8.0-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap
The new openfortivpn upstream release added an AC_TRY_RUN check and that
makes it fail to cross build again. The check doesn't actually need to
be run. Compiling is sufficient here. The attached patch fixes that.
openfortivpn also uses AC_CHECK_FILE for /usr/sbin/ppp and
/usr/sbin/pppd. Given that the pppd location is given on command line, I
wonder whether these checks are necessary. Also the openfortivpn binary
package does not depend on pppd. This looks all very strange. Maybe you
can have a look?
Given sufficient cache variables, the attached patch makes openfortivpn
cross buildable. Please consider applying it.
Helmut
--- openfortivpn-1.8.0.orig/configure.ac
+++ openfortivpn-1.8.0/configure.ac
@@ -191,7 +191,7 @@
# Specialised checks for particular features.
AC_MSG_CHECKING(whether rtentry is available and has rt_dst )
-AC_TRY_RUN([
+AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
#include <sys/types.h>
#include <sys/socket.h>
#include <net/route.h>
@@ -199,11 +199,10 @@
{
return (struct sockaddr_in *) addr;
}
+],[
struct rtentry route;
-int main() {
cast_addr(&(&route)->rt_dst)->sin_family = AF_INET;
- return (cast_addr(&(&route)->rt_dst)->sin_family == AF_INET) ? 0 : 1; }
-], [
+])],[
AC_DEFINE(HAVE_RT_ENTRY_WITH_RT_DST)
AC_MSG_RESULT(yes)
], AC_MSG_RESULT(no) )
