From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jesse Zhang <sen.zhang@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] coreutils: remove dependency on coreutils-native
Date: Thu, 17 Jan 2013 20:22:08 +0000 [thread overview]
Message-ID: <1358454128.27799.5.camel@ted> (raw)
In-Reply-To: <50F796EF.3040900@windriver.com>
On Thu, 2013-01-17 at 14:15 +0800, Jesse Zhang wrote:
> On 01/17/2013 01:37 PM, Kamble, Nitin A wrote:
> > This is bit old (out of my cached memory), but looking at my commit (543577c25b5a4e89a3ab15ee28e754b71c2a43d5) the dependency on coreutils-native is needed if the build system does not have coreutils, or it is not compatible with the sources of the coreutils you are trying to build. And the commit log does show the errors it was hitting, which are solved by using the native version of the coreutils.
>
> Thanks Nitin. But I don't think there can be any system without
> coreutils. And if there is some compatibility issue (which I haven't been
> able to reproduce on our various hosts), we should be able to trace it
> down to a specific command within coreutils.
>
> Do you still have some notes on how to reproduce the error?
Looks like its related to help2man. The native versions were being
generated so help2man could generate the man pages correctly. We should
just patch out the generation (or regeneration?) of the man pages...
Cheers,
Richard
prev parent reply other threads:[~2013-01-17 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 7:16 [PATCH] coreutils: remove dependency on coreutils-native Jesse Zhang
2013-01-15 7:16 ` Jesse Zhang
2013-01-16 11:59 ` Richard Purdie
2013-01-17 2:09 ` Jesse Zhang
2013-01-17 5:37 ` Kamble, Nitin A
2013-01-17 6:15 ` Jesse Zhang
2013-01-17 20:22 ` 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=1358454128.27799.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sen.zhang@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