From: Andreas Bachmann <bacr@zhaw.ch>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] execvp: /bin/sh: Argument list too long
Date: Wed, 21 Nov 2012 15:02:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20121121T152303-3@post.gmane.org> (raw)
In-Reply-To: <4F2C5474.6060702@erwinrol.com>
Erwin Rol <mailinglists@...> writes:
> and that seems to make the difference. On a other machine where the
> /home/erwin/ part is longer it fails in the same way with a
> arm-tegra2-linux-gnueabi (without _hardfloat part).
>
> It seems the setup is really stretching the limits of the system. It
> might be an idea to shortening the PTXCONF_PLATFORM part in the
> Toolchain project by default.
>
> - Erwin
>
>
I have sort of the or related problem in ptxdist-2012.10.0 and
OSELAS.Toolchain-2011.11.3.
In the Makefile [1] [2] at target "install-plugin" there is an inline-script
(setting variables and loop over the headers), who can't be executed:
headers=`echo $(PLUGIN_HEADERS) | tr ' ' '\012' | sort -u`
"make: execvp: /bin/bash: Argument list too long"
My build system: Ubuntu 12.10 Alpha 3
I found a bugfix [1]. Just replace
headers=`echo $(PLUGIN_HEADERS) | tr ' ' '\012' | sort -u`
with
headers="$(sort $(PLUGIN_HEADERS))"; \
and the make-process starts again.
[1] Path:
OSELAS.Toolchain-2011.11.3/platform-arm-v5te-linux-gnueabi-gcc-4.6.2-glibc-
2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2-first-
build/gcc/Makefile
[2] Path:
OSELAS.Toolchain-2011.11.3/platform-arm-v5te-linux-gnueabi-gcc-4.6.2-glibc-
2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2-build/gcc
/Makefile
[3] http://patches.openembedded.org/patch/29825/
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-11-21 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 18:05 Erwin Rol
2012-02-03 21:28 ` Michael Olbrich
2012-02-03 21:41 ` Erwin Rol
2012-11-21 15:02 ` Andreas Bachmann [this message]
2012-12-10 9:10 ` Michael Olbrich
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=loom.20121121T152303-3@post.gmane.org \
--to=bacr@zhaw.ch \
--cc=ptxdist@pengutronix.de \
/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