Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <Qi.Chen@windriver.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] [V2] Make poky work correctly with long TMPDIR
Date: Fri, 30 Nov 2012 18:37:40 +0800	[thread overview]
Message-ID: <50B88C74.5040001@windriver.com> (raw)
In-Reply-To: <cover.1354084523.git.Qi.Chen@windriver.com>

On 11/30/2012 06:33 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi<Qi.Chen@windriver.com>
>
> Poky had a problem with long TMPDIR.
> If the TMPDIR had a length of 410 chars, for example, the world building
> would fail for three reasons.
> 1) autotools.bbclass: With long TMPDIR, aclocal would have a very long argument
>     list whick makes building some packages (coretuils for example) fail.
> 2) qt4-native: It hardcodes some static char arrays to be 256.
> 3) ghostscript: It configures its MAX_TOKEN to be 256.
>
> This series of patches are aimed at making poky building system working correctly with long TMPDIR.
> The three patches solve the three above problems respectively.
>
> [Version 2 fixes the indentation problem in my last patch]
>
> The following changes since commit 0d7d413d64bab8d3c758414c6c8c653ccc325653:
>
>    build-appliance-image: Update to dee77eca39f406f90e60d9c5ef7a66fcc8f57dbf commit (2012-11-21 20:40:43 +0000)
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib ChenQi/autotools
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/autotools
>
> Chen Qi (3):
>    autotools.bbclass: use relative path for acpaths whenever possible
>    qt4-native: make qt4-native work with long building path
>    ghostscript: make ghostscript work with long building path
>
>   meta/classes/autotools.bbclass                     |   14 ++--
>   ...tscript-work-with-long-building-directory.patch |   19 +++++
>   .../ghostscript/ghostscript_9.05.bb                |   10 +--
>   ...e-qt4-native-work-with-long-building-path.patch |   82 ++++++++++++++++++++
>   meta/recipes-qt/qt4/qt4-native.inc                 |    3 +-
>   5 files changed, 116 insertions(+), 12 deletions(-)
>   create mode 100644 meta/recipes-extended/ghostscript/ghostscript/0001-make-ghostscript-work-with-long-building-directory.patch
>   create mode 100644 meta/recipes-qt/qt4/qt4-4.8.3/0001-make-qt4-native-work-with-long-building-path.patch
>
Sorry for my carelessness. Please ignore this version.
The upstream status is incorrect.



      parent reply	other threads:[~2012-11-30 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  3:08 [PATCH 0/3] Make poky work correctly with long TMPDIR Qi.Chen
2012-11-30  3:08 ` [PATCH 1/3] autotools.bbclass: use relative path for acpaths whenever possible Qi.Chen
2012-12-04  2:57   ` ChenQi
2012-12-04  8:39     ` Richard Purdie
2012-12-04  9:03       ` ChenQi
2012-11-30  3:08 ` [PATCH 2/3] qt4-native: make qt4-native work with long building path Qi.Chen
2012-11-30  7:46   ` Martin Jansa
2012-11-30  8:01     ` ChenQi
2012-11-30  8:11       ` Martin Jansa
2012-11-30  9:05         ` ChenQi
2012-11-30  3:08 ` [PATCH 3/3] ghostscript: make ghostscript " Qi.Chen
2012-11-30 10:37 ` ChenQi [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=50B88C74.5040001@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=Zhenfeng.Zhao@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