Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Remove readline for which
Date: Tue, 5 Aug 2008 22:05:57 +0200	[thread overview]
Message-ID: <20080805200557.GM9208@mx.loc> (raw)
In-Reply-To: <bbbeeccd0808051244k582789fdtae270bde1ac4aa1b@mail.gmail.com>

Hi Wade, *,

On Tue, Aug 05, 2008 at 01:44:50PM -0600, Wade Berrier wrote:
>Hi,
>
>I've patched 'which' to not require readline on the source level
>instead of selecting it on the buildroot dependency level.

I suggest you try to get that fixed upstream so they do allow for
./configure --disable-readline-and-yes-i-really-do-not-want-it

Short of that, why don't you use busybox in the first place?

I'm really curious how big your "fixed" which binary is?

Mine looks like this, perhaps your's is smaller?
$ size debianutils/which.o
   text	   data	    bss	    dec	    hex	filename
    211	      0	      0	    211	     d3	debianutils/which.o

Just to give you some background: buildroot is ment to serve as an
environment for uClibc. That's it's primary goal AFAIU. Second, it's
ment to serve as an easy way to get you a _small_ filesystem (thus using
busybox targeted at uClibc).

There is really no reason why .._HIDE_OTHER is visible to a casual user
since it's not ment to be actually used, but just to test uClibc, in my
POV. Please, just set BR2_PACKAGE_BUSYBOX_HIDE_OTHERS=y in your toplevel
.config.
>
>Patch attached.

As said. Re-read the patch. Send it to the maintainers of "debianutils"
and understand why they will most likely reject it in it's current form.
HTH,

  reply	other threads:[~2008-08-05 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 19:44 [Buildroot] [PATCH] Remove readline for which Wade Berrier
2008-08-05 20:05 ` Bernhard Fischer [this message]
2008-08-06 14:48   ` Wade Berrier
2008-08-06 16:04     ` Wade Berrier

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=20080805200557.GM9208@mx.loc \
    --to=rep.dot.nop@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