Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4] coreutils: Move stdbuf into an own package coreutils-stdbuf
Date: Thu, 31 Oct 2019 14:28:29 +0200	[thread overview]
Message-ID: <20191031122828.GA31854@localhost> (raw)
In-Reply-To: <e3ede03b-34b7-4815-c5e3-cfc5eb6d8495@windriver.com>

On Wed, Oct 30, 2019 at 04:36:58PM -0400, Randy MacLeod wrote:
> On 10/28/19 6:13 PM, Adrian Bunk wrote:
> > This LD_PRELOAD trick is not really suitable for busybox,
> > so can be the only part of coreutils needed.
> 
> Which LD_PRELOAD trick?
> 
> Ah, I think you mean:
> 
>    The coreutils implementation of stdbuf uses LD_PRELOAD [1]
>    to dynamically load libstdbuf which calls setvbuf().
>    This can't be implemented simply in busybox since it produces
>    one or two statically linked executables. Therefore, stdbuf
>    should be packaged separately.
> 
> [1]  ?? http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=src/stdbuf.c;h=7eaadb45fef8c01783eeb5c27853fafbcef34f1c;hb=HEAD#l188
> 
> Could you send a v5 for plebs like me?

Done.

> ../Randy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      reply	other threads:[~2019-10-31 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 22:13 [PATCH v4] coreutils: Move stdbuf into an own package coreutils-stdbuf Adrian Bunk
2019-10-30 20:36 ` Randy MacLeod
2019-10-31 12:28   ` Adrian Bunk [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=20191031122828.GA31854@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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