On (11/09/12 20:18), Austin Zhang wrote:
>    > successful configure itself is useless, build is the one that matters.
>    Yes, I agree this, I just mean "not install genl is not the excuse of fail
>    to configure in _above_ cases". 

sorry, not sure.
missing dependency is a very good reason to fail configure. in fact, configure is performed
to validate system if it fits minimum build requirements. and in our case missing libnl
and libnl-genl are a show stoppers.

but yes, we have a problem with that ubuntu package mess that we have to address.

>    After double check, in libnl-3 of ubuntu 11.10 (sorry, I wrote it as 11.04
>    in above email) includes these content of lib-genl, so in 11.10, no
>    libnl-genl, which only is in 12.04, where the nl version is: 3.2.3.
>    and for libnl2, also no genl.
>

is this correct?

ubuntu  libnl-3.*.so    libnl-genl-3.*.so       libnl-2.*.so    libnl-genl-2.*.so
11.10   +               -                       +               -
12.04   +               +                       +               +


is 11.10 still supported? if support for that version is discontinued then I'm not sure
we really must care.

        -ss


>    2012/11/9 Sergey Senozhatsky <[1]sergey.senozhatsky@gmail.com>
>
>      On (11/09/12 19:43), Austin Zhang wrote:
>      >    >�but there are no evidence of,
>      >    nl-gen will only impact compile rather than configure, right?
>      >    Those above build time error will happen in upstream version if you
>      only
>      >    install libnl3 but libnl-genl-3 for libnl3 case.
>      >    But anyway, it shouldn't impact 'configure' action.�
>      >
>
>      disagree, successful configure itself is useless, build is the one that
>      matters.
>      if one does not have all requirements for build, failed configure is ok.
>
>              -ss
>

>      >    2012/11/9 Sergey Senozhatsky <[1][2]sergey.senozhatsky@gmail.com>

>      >
>      >      On (11/09/12 19:17), Austin Zhang wrote:
>      >      > � �libnl3:
>      >      > � �libnl-3.0 � � � � � � � � � � �libnl - Convenience library
>      for
>      >      netlink
>      >      > � �sockets
>      >      > � �libnl2:
>      >      > � �libnl-2.0 � � � � � � � � � � �libnl - Convenience library
>      for
>      >      netlink
>      >      > � �sockets
>      >      >
>      >
>      >      so, libnl-3.0.pc and libnl-2.0.pc are there, but there are no
>      evidence
>      >      of, for example,
>      >      libnl-genl
>      >
>      >      pkg-config output on Arch
>      >      libnl-3.0 � � � � � � � � � libnl - Convenience library for
>      netlink
>      >      sockets
>      >      libnl-cli-3.0 � � � � � � � libnl-cli - Command Line Interface
>      library
>      >      for netlink sockets
>      >      libnl-nf-3.0 � � � � � � � �libnl-nf - Netfilter Netlink Library
>      >      libnl-route-3.0 � � � � � � libnl-route - Netlink Routing Family
>      Library
>      >      libnl-genl-3.0 � � � � � � �libnl-genl - Generic Netlink Library
>      >
>      >      in case if we remove libnl-genl from PKG_CHECK_MODULES, we'll
>      break the
>      >      build, because LIBNL_LIBS
>      >      should be '-lnl-genl-3 -lnl-3', not just '-lnl-3'.
>      >
>      >      [..]
>      >      src/tuning/iw.c:89: undefined reference to `genl_connect'
>      >      src/tuning/iw.c:95: undefined reference to
>      `genl_ctrl_alloc_cache'
>      >      src/tuning/iw.c:101: undefined reference to
>      `genl_ctrl_search_by_name'
>      >      and so on...
>      >
>      >      looks like we need to workaround ubuntu.
>      >
>      >      � � � � -ss
>      >
>      > References
>      >
>      >    Visible links

>      >    1. mailto:[3]sergey.senozhatsky@gmail.com

>
> References
>
>    Visible links
>    1. mailto:sergey.senozhatsky@gmail.com

>    2. mailto:sergey.senozhatsky@gmail.com
>    3. mailto:sergey.senozhatsky@gmail.com