All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/dhcp: always disable zlib in bind library
Date: Tue, 23 Apr 2019 09:48:38 +0200	[thread overview]
Message-ID: <CAPi7W83GeG-wXs8soJBPtve7-Nxj4EcG=yV0v2CzPP+2Y6P9hQ@mail.gmail.com> (raw)
In-Reply-To: <20190423092825.0da99fd2@windsurf>

Hello Thomas,

Le mar. 23 avr. 2019 ? 09:28, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> a ?crit :
>
> Hello Fabrice,
>
> On Mon, 22 Apr 2019 23:19:04 +0200
> Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
>
> > > Thanks to this, zlib is properly built before dhcp, and everything
> > > works fine.
> > This is strange because I think I also tried this fix and the build
> > failure was not fixed because if no value is provided to zlib, the
> > configure script will try to find zlib header on host (see
> > dhcp/bind/bind-9.11.2-P1/configure.in):
> >
> >     auto|yes)
> >         for d in /usr /usr/local /opt/local
> >         do
> >             if test -f "${d}/include/zlib.h"
> >             then
> >                 if test ${d} != /usr
> >                 then
> >                     zlib_cflags="-I ${d}/include"
> >                     LIBS="$LIBS -L${d}/lib"
> >                 fi
> >                 have_zlib="yes"
> >             fi
> >         done
> >         ;;
> >
> > And obviously, build will fail if those headers are found on host.
> > So I think, we should also set --with-zlib=$(STAGING_DIR)/usr but it
> > was also failing.
>
> Hum, OK, I see. I do have the Zlib development files installed on my
> system though, and /usr/include/zlib.h exists.
>
> > I'll investigate a little more to find why if you think that disabling
> > zlib is not a good solution.
>
> OK. Actually, it was not really well explained in your commit log /
> comment what the problem was. It felt like "it doesn't work, so let's
> take the easy route". If indeed the zlib detection is too broken, I'm
> perfectly fine with disabling it. But the reason is not "let's disable
> it like other dependencies".
I'll send a v2 this evening to fix the zlib detection or to improve
the commit message.
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Best Regards,

Fabrice

      reply	other threads:[~2019-04-23  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21 17:10 [Buildroot] [PATCH 1/1] package/dhcp: always disable zlib in bind library Fabrice Fontaine
2019-04-22 20:39 ` Thomas Petazzoni
2019-04-22 21:19   ` Fabrice Fontaine
2019-04-23  7:28     ` Thomas Petazzoni
2019-04-23  7:48       ` Fabrice Fontaine [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='CAPi7W83GeG-wXs8soJBPtve7-Nxj4EcG=yV0v2CzPP+2Y6P9hQ@mail.gmail.com' \
    --to=fontaine.fabrice@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.