From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/bind: fix compile/linking failure
Date: Mon, 14 Dec 2020 21:48:25 +0100 [thread overview]
Message-ID: <X9fPmTg1tcXw8rZR@pevik> (raw)
In-Reply-To: <X9fOqhygcYoZlh1D@pevik>
> Hi Peter,
> > Fixes:
> > - http://autobuild.buildroot.net/results/966a3de94aa97fa8e9895eede29c9cbfb4bd7301
> > .../host/lib/gcc/arm-buildroot-linux-musleabihf/9.3.0/../../../../arm-buildroot-linux-musleabihf/bin/ld: warning: libisccfg.so.163, needed by ../../lib/bind9/.libs/libbind9.so, not found (try using -rpath or -rpath-link)
> > .../host/lib/gcc/arm-buildroot-linux-musleabihf/9.3.0/../../../../arm-buildroot-linux-musleabihf/bin/ld: ../../lib/bind9/.libs/libbind9.so: undefined reference to `cfg_obj_line'
> Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
> Thanks for your fix, LGTM.
> Have you tried to send your patch upstream (I haven't seen it in
> https://gitlab.isc.org/isc-projects/bind9/-/merge_requests).
> BTW I'll probably update bind to 9.16.8 soon (following suggestion from Peter Korsgaard).
I mean 9.16.9
Kind regards,
Petr
> https://kb.isc.org/docs/aa-01540
> BIND 9.11 is our Extended Support Version, supported until December, 2021.
> BIND 9.16 will be our next ESV, followed by BIND 9.20; every second stable version after that will be ESV
> But your patch will be needed for both.
> Kind regards,
> Petr
next prev parent reply other threads:[~2020-12-14 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 20:20 [Buildroot] [PATCH v1] package/bind: fix compile/linking failure Peter Seiderer
2020-12-14 20:44 ` Petr Vorel
2020-12-14 20:48 ` Petr Vorel [this message]
2020-12-14 20:53 ` Peter Seiderer
2020-12-14 21:19 ` Peter Seiderer
2020-12-14 21:49 ` Bernd Kuhls
2020-12-14 22:11 ` Peter Seiderer
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=X9fPmTg1tcXw8rZR@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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