mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] error when compiling toolchain for arm-cortexa8
Date: Fri, 14 Dec 2012 10:49:33 +0100	[thread overview]
Message-ID: <20121214094933.GE32091@pengutronix.de> (raw)
In-Reply-To: <emc86d78b1-3851-48d6-9eca-35320848b7c3@plh001-think>

On Thu, Dec 13, 2012 at 02:27:22PM +0000, Dr. Patrick Langfeld wrote:
> Hi,
> We have a problem when compiling the arm-cortexa8 toolchain with
> ptxdist.
> What we did is: download from http://www.pengutronix.de/software/ptxdist/download/ptxdist-2012.10.0.tar.bz2
> unpacking
>   tar -xf OSELAS.Toolchain-2011.11.3.tar.bz2
>  changing into project dir OSELAS.Toolchain-2011.11.3 and creating a
> softlink with
>     ln -s /usr/local/bin/ptxdist-2012.10.0 ptx
> configuring and start build with
>   ./ptx select ptxconfigs/arm-cortexa8-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig
>   ./ptx go --force

Don't do this. Always build the toolchain with the ptxdist version it was
configured for.

> 
> 
> We got the following error:
> 
> new error: make[3]: Leaving directory `/home/delaitre/src/optimeas-ptxdist/toolchains/OSELAS.Toolchain-2011.11.3/platform-arm-cortexa8-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-linaro-4.6-2011.11-first-build/gcc'
> make[2]: Leaving directory `/home/delaitre/src/optimeas-ptxdist/toolchains/OSELAS.Toolchain-2011.11.3/platform-arm-cortexa8-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-linaro-4.6-2011.11-first-build'
> make[1]: Leaving directory `/home/delaitre/src/optimeas-ptxdist/toolchains/OSELAS.Toolchain-2011.11.3/platform-arm-cortexa8-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-linaro-4.6-2011.11-first-build'
> make[3]: execvp: /bin/bash: Argument list too long
> make[3]: *** [install-plugin] Error 127
> make[2]: *** [install-gcc] Error 2
> make[1]: *** [install] Error 2
> make: *** [/home/delaitre/src/optimeas-ptxdist/toolchains/OSELAS.Toolchain-2011.11.3/platform-arm-cortexa8-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/state/cross-gcc-first.install]
> Error 2
> 
> Any idea what went wrong?

Make calls 'echo' with many absolute paths inside
gcc-linaro-4.6-2011.11-first-build. The resulting argument list is too long
for bash to handle. This is a known issue. You have two options:
1. Make sure the absolute paths are shorter by building e.g. in
/home/delaitre/src/OSELAS.Toolchain-2011.11.3/ (I think this is short
enough).
2. Use the new 2012.12.0 Toolchain. I've applied a patch that should fix
this.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2012-12-14  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 14:27 Dr. Patrick Langfeld
2012-12-14  9:49 ` Michael Olbrich [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=20121214094933.GE32091@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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