From: "Eugen.Hristev--- via buildroot" <buildroot@buildroot.org>
To: <fontaine.fabrice@gmail.com>, <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: untar internal bind
Date: Thu, 21 Apr 2022 09:24:51 +0000 [thread overview]
Message-ID: <2507ebbe-3dc4-e2a2-f3e8-f668603b52d8@microchip.com> (raw)
In-Reply-To: <20220419161130.3431492-1-fontaine.fabrice@gmail.com>
On 4/19/22 7:11 PM, Fabrice Fontaine wrote:
> 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
>
> Fixes:
> - http://autobuild.buildroot.org/results/d25b76e628ffe5293c6bc1fd467a6b8966cb1bc2
> - http://autobuild.buildroot.org/results/ba3258d8df00a7626784189125f0202fb161c40e
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Tested-by: Eugen Hristev <eugen.hristev@microchip.com>
Tested on AT91 boards
> ---
> 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
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-21 9:25 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 [this message]
2022-04-21 19:32 ` Yann E. MORIN
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=2507ebbe-3dc4-e2a2-f3e8-f668603b52d8@microchip.com \
--to=buildroot@buildroot.org \
--cc=Eugen.Hristev@microchip.com \
--cc=fontaine.fabrice@gmail.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.