From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] [PATCH] bjam-native: 1.65.1 -> 1.66.0
Date: Sun, 07 Jan 2018 09:42:18 +0000 [thread overview]
Message-ID: <1515318138.29722.24.camel@linuxfoundation.org> (raw)
In-Reply-To: <1515227515-18557-1-git-send-email-huangqy.fnst@cn.fujitsu.com>
On Sat, 2018-01-06 at 16:31 +0800, Huang Qiyu wrote:
> 1.Upgrade bjam-native form 1.65.1 to 1.66.0
> 2.Upgrade boost form 1.65.1 to 1.66.0
>
> Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
https://autobuilder.yocto.io/builders/nightly-musl/builds/700/steps/BuildImages/logs/stdio
Applying patch 0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch
patching file tools/build/src/tools/gcc.jam
Hunk #1 FAILED at 1068.
1 out of 1 hunk FAILED -- rejects in file tools/build/src/tools/gcc.jam
Patch 0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch does not apply (enforce with -f)
Along with around 30 other occurrences of a similar error. Does make me
wonder how that was tested?
Cheers,
Richard
next prev parent reply other threads:[~2018-01-07 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 8:31 [PATCH] [PATCH] bjam-native: 1.65.1 -> 1.66.0 Huang Qiyu
2018-01-07 9:42 ` Richard Purdie [this message]
2018-01-07 12:19 ` Alexander Kanavin
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=1515318138.29722.24.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=huangqy.fnst@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox