From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ChenQi <Qi.Chen@windriver.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] autotools.bbclass: use relative path for acpaths whenever possible
Date: Tue, 04 Dec 2012 08:39:45 +0000 [thread overview]
Message-ID: <1354610385.25268.28.camel@ted> (raw)
In-Reply-To: <50BD667C.6040005@windriver.com>
On Tue, 2012-12-04 at 10:57 +0800, ChenQi wrote:
> Hi Richard,
>
> I saw that this series of patches have been merged except this one.
> Is there any problem with this patch?
>
> The thing is, if we don't fix autotool.bbclass like this, building
> coreutils will fail with a long TMPDIR (bug#2766). I tried to build
> coretuils with TMPDIR of 200 char length, it failed.
I know but I'm rather unhappy having the autotools code work two rather
different ways depending on the number of configure scripts a project
has, it all seems like a bit of a hack :(
I don't like the fix but I haven't found time to propose any
alternative...
Cheers,
Richard
next prev parent reply other threads:[~2012-12-04 8:54 UTC|newest]
Thread overview: 13+ 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 [this message]
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 ` [PATCH 0/3] [V2] Make poky work correctly with long TMPDIR ChenQi
[not found] <cover.1354265260.git.Qi.Chen@windriver.com>
2012-11-30 10:33 ` [PATCH 1/3] autotools.bbclass: use relative path for acpaths whenever possible Qi.Chen
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=1354610385.25268.28.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=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