From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Sanil kumar <sanil.kumar@huawei.com>
Subject: Re: [PATCH] boost: fix re-execution of task
Date: Sat, 14 Apr 2012 09:23:50 +0100 [thread overview]
Message-ID: <1334391830.7309.87.camel@ted> (raw)
In-Reply-To: <CAMKF1so2tFrdJgQHEcTXmN8vU4KetHL0QUjv+3=Yhi=o3DjESg@mail.gmail.com>
On Fri, 2012-04-13 at 19:14 -0700, Khem Raj wrote:
> On Fri, Apr 13, 2012 at 3:23 PM, Saul Wold <sgw@linux.intel.com> wrote:
> > On 04/13/2012 04:42 AM, Venkata ramana gollamudi wrote:
> >>
> >> After building boost package, re-execution of boostconfig task followed by
> >> re-execution of compile task is giving following error
> >> "error: duplicate initialization of gcc with the following parameters"
> >> during compilation
> >> It is because multiple entries of gcc are being added during boostconfig
> >> re-execution
> >> there by failing the compilation.
> >>
> >> The patch fixes adding multiple "Using gcc" entries into
> >> /tools/build/v2/user-config.jam
> >>
> >> [Yocto #2194]
> >>
> >> Signed-off-by: Venkata Ramana Gollamudi<ramana.gollamudi@huawei.com>
> >> ---
> >> meta/recipes-support/boost/boost.inc | 6 +++++-
> >> 1 files changed, 5 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/meta/recipes-support/boost/boost.inc
> >> b/meta/recipes-support/boost/boost.inc
> >> index d70a7e2..c9306df 100644
> >> --- a/meta/recipes-support/boost/boost.inc
> >> +++ b/meta/recipes-support/boost/boost.inc
> >> @@ -135,7 +135,11 @@ BJAM_OPTS = '${BJAM_TOOLS} \
> >> do_boostconfig() {
> >> cp -f boost/config/platform/linux.hpp
> >> boost/config/platform/linux-gnueabi.hpp
> >>
> >> - echo 'using gcc : 4.3.1 : ${CXX} : compileflags
> >> -DBOOST_SP_USE_PTHREADS -I${includedir} linkflags -L${libdir} ;'>>
> >> ${S}/tools/build/v2/user-config.jam
> >> + # D2194:Fixing the failure of "error: duplicate initialization of
> >> gcc with the following parameters" during compilation.
> >> + if ! grep -qe "^using gcc : 4.3.1"
> >> ${S}/tools/build/v2/user-config.jam
> >> + then
> >> + echo 'using gcc : 4.3.1 : ${CXX} : compileflags
> >> -DBOOST_SP_USE_PTHREADS -I${includedir} linkflags -L${libdir} ;'>>
> >> ${S}/tools/build/v2/user-config.jam
> >> + fi
> >> }
> >>
> >> addtask do_boostconfig after do_patch before do_configure
> >
> >
> > Merged into OE-Core
>
> I had some feedback on this patch series. I wonder if it was so meaningless.
I'd taken it before your feedback, the merge email was just a bit
later :(.
I'm really struggling to get fixes into the tree yet keep things
building and stable for -rc4 at the moment. I've been disappointed with
the lack of testing some patches have had. I accelerated getting some
things in so that they could get good exposure on the autobuilder at
least.
FWIW, D2194 is referencing the Yocto bugzilla, not any other internal
defect tracking system. I'll take patches to improve comments but I
really want to get some of the rebuilding issues fixed for release as
people keep hitting them and they're a pain.
Cheers,
Richard
prev parent reply other threads:[~2012-04-14 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 11:42 [PATCH] boost: fix re-execution of task Venkata ramana gollamudi
2012-04-13 18:04 ` Khem Raj
2012-04-13 22:23 ` Saul Wold
2012-04-14 2:14 ` Khem Raj
2012-04-14 8:23 ` 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=1334391830.7309.87.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sanil.kumar@huawei.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