Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] ifupdown-0.8.2 / dhcp-4.1-ESV-R12 incompatibility
Date: Sat, 9 Jan 2016 01:18:07 +0100	[thread overview]
Message-ID: <569051BF.70209@mind.be> (raw)
In-Reply-To: <568ECC28.50704@zacarias.com.ar>

On 07-01-16 21:35, Gustavo Zacarias wrote:
> 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.

 Given this brokenness, and that there are better alternatives, perhaps we
should kill the dhcp package? Or is it useful as a server? In the latter case,
we should add a warning to the ifupdown help text.

 BTW, I guess busybox ifupdown does work?

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-01-09  0:18 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
2016-01-09  0:18       ` Arnout Vandecappelle [this message]
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=569051BF.70209@mind.be \
    --to=arnout@mind.be \
    --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