public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: araimondi@gmx.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: target/5437: building arm-elf crossgcc (GCC 3.0.2) fails due to makefile error
Date: Tue, 22 Jan 2002 16:51:00 -0000	[thread overview]
Message-ID: <20020123005126.17155.qmail@sources.redhat.com> (raw)

Synopsis: building arm-elf crossgcc (GCC 3.0.2) fails due to makefile error

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Tue Jan 22 16:51:26 2002
State-Changed-Why:
    The t-arm-elf file in gcc 3.0.3 does not have spaces
    on the lines which you mention.  Perhaps the program
    which you used to extract the gcc archive converted
    the tabs to spaces for you.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5437


             reply	other threads:[~2002-01-23  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22 16:51 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15 10:06 rearnsha
2002-01-20 14:36 araimondi

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=20020123005126.17155.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=araimondi@gmx.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).