From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: fix cross build
Date: Mon, 2 Oct 2023 22:51:44 +0200 [thread overview]
Message-ID: <20231002205144.GD2957@scaer> (raw)
In-Reply-To: <20231002195159.3053254-1-bernd@kuhls.net>
Bernd, All,
On 2023-10-02 21:51 +0200, Bernd Kuhls spake thusly:
> Fixes build error
>
> Building dns library in /home/bernd/buildroot/br4/output/build/dhcp-4.4.3-
> P1/bind/bind-9.11.36/lib/dns
> ./gen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found
> (required by ./gen)
> make[4]: *** [Makefile:601: include/dns/enumtype.h] Error 1
> make[3]: *** [Makefile:595: include] Error 2
>
> with this defconfig
>
> BR2_x86_64=y
> BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
> BR2_PACKAGE_DHCP=y
>
> Please note that this build error only occurs when the target and the
> host system have the same arch. For example this defconfig builds fine:
>
> BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
> BR2_PACKAGE_DHCP=y
>
> on a Debian 12 x86_64 host using glibc-2.36:
>
> $ /lib/ld-linux.so.2 --version
> ld.so (Debian GLIBC 2.36-9+deb12u1) stable release version 2.36.
>
> The error occurs since buildroot commit 34f8d874ee which bumped glibc
> from 2.37 to 2.38.
>
> This patch is inspired by the Yocto Project:
> https://patchwork.yoctoproject.org/project/oe/patch/20230715212159.3265080-1-raj.khem@gmail.com/
That patch has an important tidbit of inoormation that yours is missing,
and that is important to get: this is passing the configure options to
the internal bind.
Indeed, I was very puzzled why passing the same --build, --host, and
--target as pkg-autotools already does, would fix the issue.
But indeed, isch dhcp internally configure a bundled bind, and messes
when doing so.
So your patch looks like it is correct.
However, I would challenge it on other grounds: ISC decided to stop
maintaing dhcp starting end of 2022, almost a year ago, when they
released the last version of dhcp.
Should we just drop that package now and be done with it?
Regards,
Yann E. MORIN.
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/dhcp/dhcp.mk | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/dhcp/dhcp.mk b/package/dhcp/dhcp.mk
> index 7be40191c8..094d361e45 100644
> --- a/package/dhcp/dhcp.mk
> +++ b/package/dhcp/dhcp.mk
> @@ -32,6 +32,9 @@ DHCP_CONF_ENV = \
> CFLAGS='$(TARGET_CFLAGS) -DISC_CHECK_NONE=1'
>
> DHCP_BIND_EXTRA_CONFIG = \
> + --build=$(GNU_HOST_NAME) \
> + --host=$(GNU_TARGET_NAME) \
> + --target=$(GNU_TARGET_NAME) \
> BUILD_CC='$(HOSTCC)' \
> BUILD_CFLAGS='$(HOST_CFLAGS)' \
> BUILD_CPPFLAGS='$(HOST_CPPFLAGS)' \
> --
> 2.39.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-02 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 19:51 [Buildroot] [PATCH 1/1] package/dhcp: fix cross build Bernd Kuhls
2023-10-02 20:51 ` Yann E. MORIN [this message]
[not found] ` <20231002205144.GD2957__28552.5928296678$1696279934$gmane$org@scaer>
2023-10-03 11:12 ` Bernd Kuhls
2023-11-09 14:57 ` Peter Korsgaard
2023-11-04 21:13 ` Thomas Petazzoni via buildroot
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=20231002205144.GD2957@scaer \
--to=yann.morin.1998@free.fr \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
/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