From: Robert Yang <liezhi.yang@windriver.com>
To: Hongxu Jia <hongxu.jia@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: saul.wold@intel.com
Subject: Re: [PATCH 1/1] make: fix invoking makeinfo failed at do_install time
Date: Tue, 29 Apr 2014 11:04:35 +0800 [thread overview]
Message-ID: <535F16C3.2090304@windriver.com> (raw)
In-Reply-To: <9f4638c7a81e5ddf79649a7611cb5317df465274.1398416012.git.hongxu.jia@windriver.com>
Tested and Reviewed by Robert Yang <liezhi.yang@windriver.com>
// Robert
On 04/25/2014 04:59 PM, Hongxu Jia wrote:
> Reproduce steps:
> $ bitbake texinfo-native
> $ bitbake make
> $ bitbake make -cdevshell
> In the devshell:
> root:make-3.82# echo "" >> doc/make.texi
> root:make-3.82# ../temp/run.do_install
>
> Failed Log:
> ...
> tmp/work/i586-poky-linux/make/3.81-r1/make-3.81/doc/make.texi:8165: @itemx must follow @item
> ...
>
> Backport from make 4.0 to fix this issue.
>
> [YOCTO #6219]
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> .../doc-make.texi-fix-itemx-must-follow-item.patch | 24 ++++++++++++++++++++++
> meta/recipes-devtools/make/make.inc | 1 +
> 2 files changed, 25 insertions(+)
> create mode 100644 meta/recipes-devtools/make/files/doc-make.texi-fix-itemx-must-follow-item.patch
>
> diff --git a/meta/recipes-devtools/make/files/doc-make.texi-fix-itemx-must-follow-item.patch b/meta/recipes-devtools/make/files/doc-make.texi-fix-itemx-must-follow-item.patch
> new file mode 100644
> index 0000000..fbbff38
> --- /dev/null
> +++ b/meta/recipes-devtools/make/files/doc-make.texi-fix-itemx-must-follow-item.patch
> @@ -0,0 +1,24 @@
> +doc/make.texi: fix @itemx must follow @item
> +
> +Upstream-Status: Backport from make 4.0
> +
> +Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> +---
> + doc/make.texi | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/doc/make.texi b/doc/make.texi
> +--- a/doc/make.texi
> ++++ b/doc/make.texi
> +@@ -8162,7 +8162,7 @@ from complicated nests of recursive @code{make} commands.
> + rarely need to specify this option since @samp{make} does it for you;
> + see @ref{-w Option, ,The @samp{--print-directory} Option}.)
> +
> +-@itemx --no-print-directory
> ++@item --no-print-directory
> + @cindex @code{--no-print-directory}
> + Disable printing of the working directory under @code{-w}.
> + This option is useful when @code{-w} is turned on automatically,
> +--
> +1.8.1.2
> +
> diff --git a/meta/recipes-devtools/make/make.inc b/meta/recipes-devtools/make/make.inc
> index 5de74e4..faf66e1 100644
> --- a/meta/recipes-devtools/make/make.inc
> +++ b/meta/recipes-devtools/make/make.inc
> @@ -6,6 +6,7 @@ HOMEPAGE = "http://www.gnu.org/software/make/"
> SECTION = "devel"
>
> SRC_URI = "${GNU_MIRROR}/make/make-${PV}.tar.bz2 \
> + file://doc-make.texi-fix-itemx-must-follow-item.patch \
> file://SCCS.patch"
>
> inherit autotools gettext
>
prev parent reply other threads:[~2014-04-29 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 8:59 [PATCH 0/1][dora] make: fix invoking makeinfo failed at do_install time Hongxu Jia
2014-04-25 8:59 ` [PATCH 1/1] " Hongxu Jia
2014-04-29 3:04 ` Robert Yang [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=535F16C3.2090304@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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