Cross compiling in yocto platform is not enabling ipv6 by default.

Issue #910 resolved
Gautam Shejwalkar created an issue

We use yocto bitback for building monit and use cross compilation. When build from yocto ipv6 is not getting enabled by default. Even if we pass --with-ipv6 same behavior.
Looks like the cross_compile is getting set to "yes" and due to that ac_cv_ipv6 is set to "no". But if I use the --with-sysroot option and not build in yocto env then ipv6 is getting enabled.

Comments (6)

  1. Tildeslash repo owner

    please can you provide access to yocto build machine? (for example duplicate the setup on AWS or something like that)

  2. Lutz Mader

    Hello,
    nice to see, someone try to build monit for small Linux systems, via Bitbake.

    We/I use Qemu to build monit for large Linux systems, like ppc64le or s390x systems (based on SLES 11 and 12). But we use the "normal make" environment to build monit for some customer systems only. Some of the packages are available for general use, see https://bitbucket.org/lutzmad/monit/downloads/

    With regards,
    Lutz

    p.s.
    Unfortunately the "monit" packages shipped by SUSE or Ubuntu (for ppc64le and s390x) are not build well, from my point of view.

  3. Tildeslash repo owner

    You can override the IPv6 test by passing “ac_cv_ipv6=yes” to configure, for example:

    ./configure ac_cv_ipv6=yes

  4. Gautam Shejwalkar reporter

    Yes tried passing ac_cv_ipv6=yes and was able to see it compiled with IPv6 enabled. Functionality wise yet to verify but --version is saying with ipv6 and also check the src/config.h file there also #define HAVE_IPV6 1 was there. Previously it was not enabled and in --version with ipv6 was not there

    root@default:/data# ./monit-tc-5.26.0 --version
    This is Monit version 5.26.0
    Built with ssl, with ipv6, with compression, with pam and with large files
    Copyright (C) 2001-2019 Tildeslash Ltd. All Rights Reserved.

  5. Log in to comment