Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/7 V2] fixes for building in long path (length = 410)
Date: Thu, 6 Apr 2017 03:05:49 -0700	[thread overview]
Message-ID: <cover.1491473008.git.liezhi.yang@windriver.com> (raw)

* V2:
  Use '/usr/bin/env foo' rather than /usr/bin/foo or /bin/foo as shebang.

// Robert

The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:

  oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir (2017-04-06 10:13:34 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/long
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/long

Robert Yang (7):
  groff: replace "perl -w" with "use warnings"
  mc: replace "perl -w" with "use warnings"
  valgrind: set ac_cv_path_PERL to /usr/bin/env perl
  m4: do_configure: fix "Argument list too long"
  guile: do_configure: fix "Argument list too long"
  autogen-native: fix POSIX_SHELL and perl
  kmod: set ac_cv_path_DOLT_BASH to /usr/bin/env bash

 .../autogen/autogen-native_5.18.12.bb              |   3 +
 ...2-autoopts-mk-tpl-config.sh-fix-perl-path.patch |  32 +++++
 meta/recipes-devtools/guile/guile_2.0.14.bb        |   3 +
 meta/recipes-devtools/m4/m4-1.4.18.inc             |   3 +
 meta/recipes-devtools/valgrind/valgrind_3.12.0.bb  |   2 +
 .../0001-replace-perl-w-with-use-warnings.patch    | 102 ++++++++++++++++
 meta/recipes-extended/groff/groff_1.22.3.bb        |   3 +
 .../0001-mc-replace-perl-w-with-use-warnings.patch | 129 +++++++++++++++++++++
 meta/recipes-extended/mc/mc_4.8.18.bb              |   3 +
 meta/recipes-kernel/kmod/kmod.inc                  |   2 +
 10 files changed, 282 insertions(+)
 create mode 100644 meta/recipes-devtools/autogen/autogen/0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch
 create mode 100644 meta/recipes-extended/groff/groff-1.22.3/0001-replace-perl-w-with-use-warnings.patch
 create mode 100644 meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch

-- 
2.11.0.rc2.dirty



             reply	other threads:[~2017-04-06 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 10:05 Robert Yang [this message]
2017-04-06 10:05 ` [PATCH 1/7] groff: replace "perl -w" with "use warnings" Robert Yang
2017-04-06 10:05 ` [PATCH 2/7] mc: " Robert Yang
2017-04-06 10:05 ` [PATCH 3/7] valgrind: set ac_cv_path_PERL to /usr/bin/env perl Robert Yang
2017-04-06 10:05 ` [PATCH 4/7] m4: do_configure: fix "Argument list too long" Robert Yang
2017-04-06 10:05 ` [PATCH 5/7] guile: " Robert Yang
2017-04-06 10:05 ` [PATCH 6/7] autogen-native: fix POSIX_SHELL and perl Robert Yang
2017-04-06 10:05 ` [PATCH 7/7] kmod: set ac_cv_path_DOLT_BASH to /usr/bin/env bash Robert Yang

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=cover.1491473008.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.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