Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libnids: disable libnet only if not available
Date: Wed, 24 Jun 2020 21:20:33 +0200	[thread overview]
Message-ID: <20200624192033.GD20645@scaer> (raw)
In-Reply-To: <20200624121742.20034-1-guillaume.bressaix@gmail.com>

Guillaume, All,

On 2020-06-24 14:17 +0200, Guillaume W. Bres spake thusly:
> libnids can be built against an existing libnet lib,
> take advantage of that.
> 
> Unfortunately, pkg-config is not available for libnet,
> so configure --with-libnet is our only option at the
> moment.
> 
> --with-libnet expects a build directory,
> not an installation path like in our context.
> We use --with-libnet=yes to skip tests that would fail.
> In this situation, 'LIBNET' goes undefined, so we
> need to define it ourselves.
> This works because we make sure -lnet is installed
> prior anything related to libnids.
> 
> Signed-off-by: Guillaume W. Bres <guillaume.bressaix@gmail.com>
> ---
>  package/libnids/libnids.mk | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/package/libnids/libnids.mk b/package/libnids/libnids.mk
> index f0330787c7..01d50879b6 100644
> --- a/package/libnids/libnids.mk
> +++ b/package/libnids/libnids.mk
> @@ -11,7 +11,21 @@ LIBNIDS_LICENSE_FILES = COPYING
>  LIBNIDS_INSTALL_STAGING = YES
>  LIBNIDS_DEPENDENCIES = host-pkgconf libpcap
>  LIBNIDS_AUTORECONF = YES
> -LIBNIDS_CONF_OPTS = --disable-libnet
> +
> +# disable libnet if not available
> +# Tests in configure.in expect --with-libnet=$build_dir
> +# not an installation patch like in our context.
> +# We use with-libnet=yes to skip the unusual paths tests.
> +# But 'LNETLIB' gets left out, so we need to define it ourselves.
> +ifeq ($(BR2_PACKAGE_LIBNET),y)
> +LIBNIDS_DEPENDENCIES += libnet
> +
> +LIBNIDS_CONF_OPTS += --with-libnet=yes \
> +	LNETLIB=-lnet \
> +	--enable-libnet

I've reordered the options in a more logical way. Additionally, when an
assignment (or any other statement) fits on a 80-char line, we don't
split it on multiple lines, so I;ve changed to:

    LIBNIDS_CONF_OPTS += --enable-libnet --with-libnet=yes LNETLIB=-lnet

and applied to master, thanks.

Regards,
Yann E. MORIN.

> +else
> +LIBNIDS_CONF_OPTS += --disable-libnet
> +endif
>  
>  # disable libglib2 if not available
>  # The test in configure.in is flawed: passing --enable-libglib would also
> -- 
> 2.20.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2020-06-24 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 12:17 [Buildroot] [PATCH 1/1] package/libnids: disable libnet only if not available Guillaume W. Bres
2020-06-24 19:20 ` Yann E. MORIN [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200624192033.GD20645@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox