public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Matt Kline <matt@bitbashing.io>
To: crossgcc@sourceware.org
Subject: Shell errors when building GCC 6.3 in parallel
Date: Wed, 21 Dec 2016 21:04:00 -0000	[thread overview]
Message-ID: <20161221210432.GA21485@fluke-mrkline> (raw)

My company has been using crosstool-NG for about a year now to build
cross-compilers for our embedded systems (largely ARM Cortex-M4 boards).
It's been invaluable - many thanks to everyone involved in the project.

We've been using GCC 6, and I'm trying to build the latest 6.3 bugfix release.
Building an x64 -> ARMv7 cross-compiler works fine, but I also need to build
x86 -> ARM compilers since a few of my coworkers still have 32-bit setups.[*]
I've had trouble with an x64->x86->ARM Canadian cross, so my approach so far
has been building the x86 toolchain in an i686 VM.

Oddly enough, when I run CT-NG in the VM (both the last release, 1.22.0, and
Git HEAD), I get some _really_ weird errors. Perusing the log,
it almost looks like there's some parse error in the shell scripts:

    [ALL  ]    /usr/bin/bash: line 2: : command not found
    [ALL  ]    /bin/sh: line 3: (cd ./zlib && : No such file or directory
    [ALL  ]    /bin/sh: line 4:   /usr/bin/make "DESTDIR=" ...  : File name too long
    [ALL  ]    /bin/sh: line 5: $'tall)': command not found

You can see some full logs at https://gist.github.com/mrkline/0a89952cd2f6284ae534fbd94b158f73

What's stranger still is that the problems go away if I set the number of
parallel jobs to 1, suggesting that it might be some concurrency problem.
Does anyone have suggestions as to what might be causing this?

FWIW, I'm on Arch Linux, which currently ships GCC 6.2.

Many thanks,

Matt Kline
Fluke Networks

[*]: We're working on fixing that ASAP, but until then...

                 reply	other threads:[~2016-12-21 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161221210432.GA21485@fluke-mrkline \
    --to=matt@bitbashing.io \
    --cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).