All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eugen.Hristev--- via buildroot" <buildroot@buildroot.org>
To: <peter@korsgaard.com>, <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: use internal bind
Date: Tue, 12 Apr 2022 11:43:10 +0000	[thread overview]
Message-ID: <34fddc8f-8710-65f9-330d-81fefe64354a@microchip.com> (raw)
In-Reply-To: <8735iifser.fsf@dell.be.48ers.dk>

On 4/12/22 2:33 PM, Peter Korsgaard wrote:
>>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> 
> Hi,
> 
>>> Hello Peter, Fabrice,
>   >>
>   >> While your patch solves the isc/boolean.h problem, now I get several
>   >> other problems when building an arm926 platform with this package :
>   >> (sam9x60ek)
>   >>
>   >> Could you help please? 2022.01.1 is broken for me atm.
> 
>   > You should apply:
>   > https://git.buildroot.net/buildroot/commit/?id=789a08dac5808401629d6fc586b7377f54ebb316
> 
> That is already in 202.02.1:
> 
> https://git.buildroot.net/buildroot/commit/?h=2022.02.x&id=0397064a9a147903e9e0c16b2506319ea4a246fb
> 
>> as well as
>   > https://patchwork.ozlabs.org/project/buildroot/patch/DU0P251MB07797CAAE80C985DC8976335E3E79@DU0P251MB0779.EURP251.PROD.OUTLOOK.COM/
> 
> Is that an ack? ;)

I am testing that patch to see if it improves anything, but as you said 
Peter, the commit above is already in my tree.
> 
>   > Having said that, I fear that dhcp will have to be removed soon due to
>   > security concerns:
>   > https://gitlab.isc.org/isc-projects/dhcp/-/issues/233
> 
> Yeah. Eugen, is there any specific reason why you use the dhcp package
> over the other DHCP clients we provide?

Historical reasons, and the fact that people have working configurations 
using this package... I was unaware that it was due to be removed.
We will try to switch to a different package in the future. Thanks for 
letting me know.
However, if the package is still in this buildroot release, it has to 
work right ?
> 
> --
> Bye, Peter Korsgaard
> 

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-12 11:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 10:03 [Buildroot] [PATCH 1/1] package/dhcp: use internal bind Fabrice Fontaine
2022-04-04  6:19 ` James Hilliard
2022-04-04 19:31 ` Arnout Vandecappelle
2022-04-04 19:55 ` Yann E. MORIN
2022-04-09 14:09 ` Peter Korsgaard
2022-04-12 11:15   ` Eugen.Hristev--- via buildroot
2022-04-12 11:22     ` Fabrice Fontaine
2022-04-12 11:33       ` Peter Korsgaard
2022-04-12 11:43         ` Eugen.Hristev--- via buildroot [this message]
2022-04-12 12:32           ` Eugen.Hristev--- via buildroot
2022-04-12 12:34           ` Peter Korsgaard
2022-04-12 18:17             ` Fabrice Fontaine
2022-04-13  7:54               ` Eugen.Hristev--- via buildroot
2022-04-13  8:29                 ` Peter Korsgaard
2022-04-14  9:10                   ` Eugen.Hristev--- via buildroot
2022-04-14  9:59                     ` Fabrice Fontaine
2022-04-14 16:44                       ` Fabrice Fontaine
2022-04-19  5:21                         ` Eugen.Hristev--- via buildroot
2022-04-19  9:08                           ` Fabrice Fontaine
2022-04-19 10:19                             ` Eugen.Hristev--- via buildroot
2022-04-19 16:12                               ` Fabrice Fontaine
2022-04-21  9:25                                 ` Eugen.Hristev--- via buildroot
2022-04-04 13:07 Edmundo Ferreira
2022-04-05  3:54 Tim Hammer
2022-04-05  6:19 ` Fabrice Fontaine
2022-04-05 12:15   ` Tim Hammer
2022-04-05 16:18     ` Peter Seiderer
2022-04-06  1:58       ` Tim Hammer
2022-04-06  7:08         ` Fabrice Fontaine
2022-04-06 12:58           ` Tim Hammer
2022-04-06 13:30             ` Fabrice Fontaine
2022-04-06 14:06               ` Fabrice Fontaine

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=34fddc8f-8710-65f9-330d-81fefe64354a@microchip.com \
    --to=buildroot@buildroot.org \
    --cc=Eugen.Hristev@microchip.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=peter@korsgaard.com \
    /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.