Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] ifupdown-0.8.2 / dhcp-4.1-ESV-R12 incompatibility
Date: Thu, 7 Jan 2016 17:35:52 -0300	[thread overview]
Message-ID: <568ECC28.50704@zacarias.com.ar> (raw)
In-Reply-To: <CA+sos7-4puPse5UehUFe3LO7DvfTattF+qUAu4n==LAdOBwYzw@mail.gmail.com>

On 07/01/16 17:30, Beno?t Th?baudeau wrote:

> I had started to look into this a few months ago, and setting
> --with-libbind=PATH to use the bind provided by Buildroot seemed to be
> a better option (in order to avoid possibly installing two instances
> of bind on the target, either standalone or inside the dhcp binaries
> if statically linked, and both bind versions were compatible at that
> time), though I have not yet tested it.

Hi Beno?t.
Let me save you some time, it doesn't work as expected.
I've tried pointing that into the bind build directory (because it needs 
some specific *.a files that i think aren't installed, besides another 
problem) but no luck, since it stills expects that to live in it's own 
build directory, try in dhcp's source dir:

find . -name Makefile.am -exec grep --with-filename ../bind/lib {} \;

...and you'll see the drastic results.

Even so with that fixed the bind package will need to get tweaked as 
well, since if you build shared-only you won't get those intermediate 
libraries built, and hence dhcp will fail as well.

All in all, it seems pretty broken.

Regards.

  reply	other threads:[~2016-01-07 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 14:26 [Buildroot] ifupdown-0.8.2 / dhcp-4.1-ESV-R12 incompatibility rdkehn at yahoo.com
2016-01-07 19:11 ` Gustavo Zacarias
2016-01-07 20:30   ` Benoît Thébaudeau
2016-01-07 20:35     ` Gustavo Zacarias [this message]
2016-01-09  0:18       ` Arnout Vandecappelle
2016-01-09 12:56         ` Benoît Thébaudeau
2016-01-09 13:09           ` Gustavo Zacarias

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=568ECC28.50704@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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