From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: untar internal bind
Date: Tue, 24 May 2022 10:20:59 +0200 [thread overview]
Message-ID: <87y1yruys4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220419161130.3431492-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Tue, 19 Apr 2022 18:11:30 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> 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>
Committed to 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-05-24 8:21 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
2022-04-21 19:34 ` Eugen.Hristev--- via buildroot
2022-05-24 8:20 ` Peter Korsgaard [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=87y1yruys4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox