Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wade Berrier <wberrier@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix util-linux dependencies
Date: Tue, 22 Jul 2008 12:03:33 -0600	[thread overview]
Message-ID: <bbbeeccd0807221103k5fd11b6fre850cf553f64742@mail.gmail.com> (raw)
In-Reply-To: <20080722151011.GA18680@real.realitydiluted.com>

Hi,

On Tue, Jul 22, 2008 at 9:10 AM,  <sjhill@realitydiluted.com> wrote:
> On Tue, Jul 22, 2008 at 08:39:14AM -0600, Wade Berrier wrote:
>>
>> On Tue, Jul 22, 2008 at 8:24 AM, Wade Berrier <wberrier@gmail.com> wrote:
>> > util-linux appears to depend on RPC support.
>> >
> Before making a wholesale change like this, you should probably look at
> the 'configure' and 'MCONFIG' files and discover exactly what RPC
> support is needed. If changing a config option to not include certain
> utilities depending on RPC is possible, then the preferred method is to
> add a patch for that instead of blindly enabling an option for the
> entire buildroot.

This patch came about because I noticed that util-linux was failing to
build at the link stage.  I looked up the symbols and it turns out
they are rpc calls. (probably nfs mount related)

So, I basically copied the same mechanism that nfs-utils uses to only
be availalbe if RPC is enabled.

But, as previously mentioned, since most people are probably going to
use busybox in lieu of util-linux, I don't see this dependency
affecting that many people (and at least it fixes the build, which is
currently broken).

Otherwise, if it's really important to have util-linux without rpc I
can go dig some more and resubmit.

Thanks!

Wade

      reply	other threads:[~2008-07-22 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 14:24 [Buildroot] [PATCH] Fix util-linux dependencies Wade Berrier
2008-07-22 14:39 ` Wade Berrier
2008-07-22 14:48   ` Bernhard Fischer
2008-07-22 15:10   ` sjhill at realitydiluted.com
2008-07-22 18:03     ` Wade Berrier [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=bbbeeccd0807221103k5fd11b6fre850cf553f64742@mail.gmail.com \
    --to=wberrier@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