public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jeremy Hall <jeremy.m0jnx@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Problem building gcc 4.9.2
Date: Mon, 11 Aug 2014 16:15:00 -0000	[thread overview]
Message-ID: <CAH6eHdR4mFYqA7B6HoWM_gcQhyPUGFt_cGGwYPmBxmLs9hLykQ@mail.gmail.com> (raw)
In-Reply-To: <CABQJvpnxweiXRJnMF3qQuZVT-wURM4XxK-Yps6jLOtMaayZhYg@mail.gmail.com>

On 11 August 2014 15:30, Jeremy Hall wrote:
> After a fresh install on Linux Mint 17 (64-bit) I am attempting to build
> the latest gcc using the following (which has worked in the past):-
>
> cd gcc-4.9.1
> contrib/download_prerequisites
> mkdir obj
> cd obj
> ../configure --disable-multilib
>
> The configure ends with the following:-
> ...
> checking where to find the target readelf... host tool
> checking where to find the target strip... host tool
> checking where to find the target windres... host tool
> checking where to find the target windmc... host tool
> checking whether to enable maintainer-specific portions of Makefiles... no
> configure: creating ./config.status
> /bin/bash: _tar: line 12: syntax error near unexpected token `('
> /bin/bash: _tar: line 12: ` ?(-)*[cr]*f)'
> /bin/bash: error importing function definition for `_tar'
> config.status: creating Makefile
> /tmp/gcc-4.9.1/obj*
>
> What am I doing wrong, or what is missing?

I've never seen that error before, there should not be a call to tar
being done there. It looks like something in your environment is
causing the problem, try to find where "_tar" is being defined (maybe
in ~/.bash_profile, ~/.bashrc or /etc/bashrc).

  reply	other threads:[~2014-08-11 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 14:30 Jeremy Hall
2014-08-11 16:15 ` Jonathan Wakely [this message]
2014-08-11 23:16 Jeremy Hall

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=CAH6eHdR4mFYqA7B6HoWM_gcQhyPUGFt_cGGwYPmBxmLs9hLykQ@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jeremy.m0jnx@gmail.com \
    /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).