public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jpmg@eng.cam.ac.uk
To: gcc-gnats@gcc.gnu.org
Subject: other/6943: problem report 6817
Date: Thu, 06 Jun 2002 01:46:00 -0000	[thread overview]
Message-ID: <200206060837.23623@tweedle.eng.cam.ac.uk> (raw)


>Number:         6943
>Category:       other
>Synopsis:       problem report 6817
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 06 01:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Patrick Gosling
>Release:        3.1
>Organization:
Cambridge University Engineering Department, UK
>Environment:
System: Linux tweedle 2.4.17-0.16smp #1 SMP Wed Mar 20 09:09:18 GMT 2002 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.1/configure --prefix=/tools/gcc/gcc-3.1-i386-rh7.2
>Description:
while doing make install, install fails with
/bin/sh: -c: line 1: syntax error near unexpected token `;'

>How-To-Repeat:
If configure and "make install" are run with the LINGUAS environment 
variable set to something other than one of the languages for which a
catalogue is provided, the CATALOGS variable will be set to the null
string, and a bash for loop in gcc/Makefile will wind up with the syntax
error outlined above.

>Fix:
Ensure that the LINGUAS environment variable is unset when building gcc,
unless you're sure this is what you want.
Meta-Fix:  ensure that this fact is documented in the INSTALL/ files.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-06-06  8:46 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=200206060837.23623@tweedle.eng.cam.ac.uk \
    --to=jpmg@eng.cam.ac.uk \
    --cc=gcc-gnats@gcc.gnu.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).