All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Julian Pidancet <julian.pidancet@gmail.com>
Subject: Re: [PATCH v2] Give coreutils a chance to build the df utility
Date: Tue, 01 Nov 2011 15:49:43 +0000	[thread overview]
Message-ID: <1320162583.15387.20.camel@ted> (raw)
In-Reply-To: <187337B8-18D1-4D7D-926C-EE015A8CD801@dominion.thruhere.net>

On Tue, 2011-11-01 at 15:21 +0100, Koen Kooi wrote:
> Op 26 okt. 2011, om 23:41 heeft Julian Pidancet het volgende geschreven:
> 
> > The coreutils configure script is unable determine how to get free
> > space from the Operating System when cross-compiling.
> > This changes caches the result of the "statfs2_bsize" test for the
> > coreutils configure script.
> > Both glibc and uclibc defines statfs as a two-argument function
> > and uses a struct statfs containing a f_bsize field. That's why
> > the fu_cv_sys_stat_statfs2_bsize variable has to be defined for
> > both libcs.
> > 
> > Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com>
> > ---
> > meta/recipes-core/coreutils/coreutils_8.14.bb |    2 +-
> > meta/site/common-glibc                        |    3 +++
> > meta/site/common-uclibc                       |    3 +++
> > 3 files changed, 7 insertions(+), 1 deletions(-)
> 
> 
> A bit late, but this is missing a PR bump, could you please send a followup patch to fix that?

I've pushed a PR bump for this myself since it saves me tracking the
issue any further.

Cheers,

Richard




      reply	other threads:[~2011-11-01 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 21:41 [PATCH v2] Give coreutils a chance to build the df utility Julian Pidancet
2011-11-01 14:21 ` Koen Kooi
2011-11-01 15:49   ` Richard Purdie [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=1320162583.15387.20.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=julian.pidancet@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.