From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Morgan Little : python-native: Put binaries in seperate directory
Date: Tue, 31 Jul 2012 11:47:00 +0100 [thread overview]
Message-ID: <1343731620.3360.9.camel@ted> (raw)
In-Reply-To: <CALbNGRQCETb5Q9WpoJDzmGwmUB7YPYhgjD21ZUUOmjwkBNGC8g@mail.gmail.com>
On Mon, 2012-07-30 at 16:08 +0200, Andreas Müller wrote:
> > Could somebody enlighten me please: What is the benefit in moving
> > python-native into a subdirectory and causing tons of recipe changes?
People were running into a problem where python-native might be
installed or uninstalled from the sysroot whilst it was being executed.
The trouble is not everything using python-native actually lists it as a
dependency. Its complicated by the fact we have the system provided
python to consider.
In general most things can use the system python. There are some which
need "our" python since they need our python libraries or deal with
their own python modules.
The best way to deal with these issue is to disentangle the python from
the system from that in sysroot and the only way I'm aware of is to
change the paths. We're unfortunately having to figure out which pieces
need the sysroot python and this is causing a few bumps. I'm sorry about
that and we're all doing our best to sort that out.
If you want stability, please use the stable release branch. We do our
best with master but we accept changes there and there is a risk that
things can break. We've always been clear about this.
> > The commit message does not help me much.
There was significant mailing list discussion about this and perlnative
which shares a similar problem.
> > To me it is just another build breaker after gobject-introspection &
> > gtk-doc. Please tell me how many further weeks we have to suffer for
> > innovations like this so I can come back then.
> >
> I forgot webkit-gtk PARALLEL_MAKE in my list
Well, gtk-doc is a sensible cleanup to make the metadata easier and most
sustainable, likewise the introspection change. We've adopting an
approach to building them endorsed by the upstream project.
The webkit-gtk parallel make issues are a pain. It takes an age to
build, parallel make speeds it up but something is broken, probably make
3.82. I'm at a loss as to how to deal with it. You can easily disable
parallel make for that recipe in your local.conf as a workaround for now
if its causing a problem (PARALLEL_MAKE_pn-webkit-gtk = "").
I'm sorry there has been some disruption, this is unfortunate but a
consequence of trying to develop things and we're all doing our best to
resolve the issues.
Cheers,
Richard
next prev parent reply other threads:[~2012-07-31 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120722104353.A204B1032B@opal>
[not found] ` <CALbNGRTJjTZZG=ysG3m+gnv0YqfaBhUEZkLF5WUJxg7-hSLGDg@mail.gmail.com>
2012-07-30 14:02 ` [oe-commits] Morgan Little : python-native: Put binaries in seperate directory Andreas Müller
2012-07-30 14:08 ` Andreas Müller
2012-07-31 10:47 ` Richard Purdie [this message]
2012-07-30 16:11 ` Little, Morgan
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=1343731620.3360.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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