From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] Fix building in very long paths
Date: Fri, 22 Jul 2011 08:17:17 -0700 [thread overview]
Message-ID: <4E29947D.1040302@linux.intel.com> (raw)
In-Reply-To: <cover.1311192464.git.tom_rini@mentor.com>
On 07/20/2011 01:08 PM, Tom Rini wrote:
> Hey all,
>
> The following series fixes building in deep paths. To be clear, the
> biggest problem is that shebang (#!) is not portable over 80 chars in
> length and we already eat up 51 chars with sysroot paths on x86_64.
> The fix, in concept is easy, use /usr/bin/env instead. In practice,
> perl makes this difficult. In this series we fix python to use
> /usr/bin/env, add a 'nativeperl' wrapper (RP's name) so that we can
> do /usr/bin/env nativeperl and not require sub-recipes to have inherit
> perlnative (eg sato-icon-theme would need perlnative if we didn't do this).
> Next we have cpan make sure it mangles everything to use nativeperl and
> then go fix a few hard cases by hand. All of these changes are either
> direct ports (python) or port + more work (perl/cpan) of changes I did
> in oe.dev. With this series I'm able to build world for qemux86 in a
> very long path (which means I could then turn on doing this in our jenkins
> cluster on the weekend like I did for oe.dev on testing-next).
>
> The following changes since commit 0d03800caffc2341b74190d38f7a372223c89f4c:
> Mei Lei (1):
> lsbsetup_1.0.bb: Change the hardcoded /usr/lib to support multilib
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib trini/work-in-deep-paths-v1
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/work-in-deep-paths-v1
>
> Tom Rini (5):
> python-native: Mangle scripts to use /usr/bin/env python, bump PR
> gnome-doc-utils: Use /usr/bin/env python in xml2po, bump PR
> perl-native: Add a perl-native wrapper in the normal bindir
> cpan.bbclass: Perform more mangling for perl path
> icon-naming-utils-native: Fix long path to perl in icon-name-mapping
>
> meta/classes/cpan.bbclass | 3 ++
> .../icon-naming-utils-native_0.8.7.bb | 7 +++-
> meta/recipes-devtools/perl/liburi-perl_1.58.bb | 2 +-
> .../perl/libxml-parser-perl_2.40.bb | 2 +-
> meta/recipes-devtools/perl/libxml-perl_0.08.bb | 2 +-
> .../perl/libxml-simple-perl_2.18.bb | 2 +-
> meta/recipes-devtools/perl/perl-native_5.12.3.bb | 17 +++++++++-
> .../recipes-devtools/python/python-native_2.6.6.bb | 5 +++
> .../sgmlspl/sgmlspl-native_1.03ii.bb | 2 +-
> .../perl/libconvert-asn1-perl_0.22.bb | 2 +-
> .../recipes-extended/perl/libtimedate-perl_1.20.bb | 2 +-
> .../perl/libxml-namespacesupport-perl_1.11.bb | 2 +-
> meta/recipes-extended/perl/libxml-sax-perl_0.96.bb | 2 +-
> .../use-usr-bin-env-for-python-in-xml2po.patch | 33 ++++++++++++++++++++
> meta/recipes-gnome/gnome/gnome-doc-utils_0.20.6.bb | 5 ++-
> 15 files changed, 75 insertions(+), 13 deletions(-)
> create mode 100644 meta/recipes-gnome/gnome/gnome-doc-utils/use-usr-bin-env-for-python-in-xml2po.patch
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into oe-core
Thanks
Sau!
prev parent reply other threads:[~2011-07-22 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 20:08 [PATCH 0/5] Fix building in very long paths Tom Rini
2011-07-20 20:08 ` [PATCH 1/5] python-native: Mangle scripts to use /usr/bin/env python, bump PR Tom Rini
2011-07-20 20:08 ` [PATCH 2/5] gnome-doc-utils: Use /usr/bin/env python in xml2po, " Tom Rini
2011-07-20 20:08 ` [PATCH 3/5] perl-native: Add a perl-native wrapper in the normal bindir Tom Rini
2011-07-20 20:08 ` [PATCH 4/5] cpan.bbclass: Perform more mangling for perl path Tom Rini
2011-07-20 20:09 ` [PATCH 5/5] icon-naming-utils-native: Fix long path to perl in icon-name-mapping Tom Rini
2011-07-22 15:17 ` Saul Wold [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=4E29947D.1040302@linux.intel.com \
--to=sgw@linux.intel.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