public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/2620: Filenames differ only in case - irix issue
Date: Wed, 27 Mar 2002 13:36:00 -0000	[thread overview]
Message-ID: <20020327213602.12213.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/2620; it has been noted by GNATS.

From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: <gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-patches@gcc.gnu.org>
Cc: <echristo@redhat.com>
Subject: Re: other/2620: Filenames differ only in case - irix issue
Date: Thu, 28 Mar 2002 08:33:23 +1100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
 gcc&pr=3D2620
 
 I would like to resolve this issue before 3.1 is released.  It has=20
 been hanging around for a year, it messes up tarballs on windows and=20
 casue me cvs warnings every day on cygwin.
 
 In the source tree we have=20
  - libffi/src/mips/n32.S
  - libffi/src/mips/n32.s
  - libffi/src/mips/o32.S
  - libffi/src/mips/o32.s
 The *.s just include the *.S
 
 The *.S are used when building libffi (for mips) using gcc.  The *.s are
 supposed to be used when building libffi with MIPSPro cc, but doesn't =
 work
 due to Makefile bitrot - MIPSPro cc does not accept gcc flags.
 
 I propose removing libffi/src/mips/n32.s and libffi/src/mips/o32.s from =
 the CVS tree.
 
 
 2002-03-28  David Billinghurst <David.Billinghurst@riotinto.com>
 
 	PR other/2620
 	* src/mips/n32.s: Delete
 	* src/mips/o32.s: Delete
 
 
 


             reply	other threads:[~2002-03-27 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 13:36 Billinghurst, David (CRTS) [this message]
2002-03-27 16:16 Eric Christopher
2002-03-28 10:36 Mark Mitchell

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=20020327213602.12213.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.com \
    --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).