From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Eugen Hristev <eugen.hristev@microchip.com>,
Jan Havran <havran.jan@email.cz>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: untar internal bind
Date: Thu, 21 Apr 2022 21:32:22 +0200 [thread overview]
Message-ID: <20220421193222.GP2730@scaer> (raw)
In-Reply-To: <20220419161130.3431492-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2022-04-19 18:11 +0200, Fabrice Fontaine spake thusly:
> Untar internal bind so libtool patches will be applied on bind's
> libtool. This will fix:
> - installation of some libraries such as libisccfg. Indeed, if libtool
> is not patched those libraries will be "relinked" and so not
> installed.
> - build failures with riscv and or1k:
>
> Invalid configuration `riscv64-buildroot-linux-musl': machine `riscv64-buildroot' not recognized
>
> Invalid configuration `or1k-buildroot-linux-uclibc': machine `or1k-buildroot' not recognized
dhcp, the package that keeps on giving...
Jan, Eugen, what keeps you from switching away from dhcp?
> Fixes:
> - http://autobuild.buildroot.org/results/d25b76e628ffe5293c6bc1fd467a6b8966cb1bc2
> - http://autobuild.buildroot.org/results/ba3258d8df00a7626784189125f0202fb161c40e
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/dhcp/dhcp.mk | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/package/dhcp/dhcp.mk b/package/dhcp/dhcp.mk
> index e6f4c419f4..f815c6c802 100644
> --- a/package/dhcp/dhcp.mk
> +++ b/package/dhcp/dhcp.mk
> @@ -14,6 +14,13 @@ DHCP_CPE_ID_VENDOR = isc
> # internal bind does not support parallel builds.
> DHCP_MAKE = $(MAKE1)
>
> +# untar internal bind so libtool patches will be applied on bind's libtool
> +define DHCP_UNTAR_INTERNAL_BIND
> + $(TAR) xf $(@D)/bind/bind.tar.gz -C $(@D)/bind/
> +endef
> +
> +DHCP_POST_EXTRACT_HOOKS = DHCP_UNTAR_INTERNAL_BIND
> +
> # use libtool-enabled configure.ac
> define DHCP_LIBTOOL_AUTORECONF
> cp $(@D)/configure.ac+lt $(@D)/configure.ac
> --
> 2.35.1
>
> _______________________________________________
> 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:[~2022-04-21 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 16:11 [Buildroot] [PATCH 1/1] package/dhcp: untar internal bind Fabrice Fontaine
2022-04-20 9:13 ` Jan Havran
2022-04-21 9:24 ` Eugen.Hristev--- via buildroot
2022-04-21 19:32 ` Yann E. MORIN [this message]
2022-04-21 19:34 ` Eugen.Hristev--- via buildroot
2022-05-24 8:20 ` Peter Korsgaard
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=20220421193222.GP2730@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=eugen.hristev@microchip.com \
--cc=fontaine.fabrice@gmail.com \
--cc=havran.jan@email.cz \
/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