public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Subject: other/2620: Filenames differ only in case
Date: Mon, 23 Apr 2001 21:26:00 -0000	[thread overview]
Message-ID: <20010424041951.919.qmail@sourceware.cygnus.com> (raw)

>Number:         2620
>Category:       other
>Synopsis:       Filenames differ only in case
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 23 21:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        gcc 3.x
>Organization:
>Environment:
all
>Description:
This summarizes discussion on gcc@gcc.gnu.org on/about 11 April 2001.  It is a minor annoyance that should be fixed one day.

In the source tree we have 
*	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

This causes some warnings when using CVS on cygwin, but fortunately the files aren't used on cygwin.  There is the potential to cause problems building a cross compiler, etc.

Tom Tromey suggested a fix

>How-To-Repeat:

>Fix:
>From Tom Tromey <tromey@redhat.com>:

My suggestion is to copy *.S to *.s (if you look at the .s files you'll see they are just #include <> anyway), update Makefile.am, and make sure to pass `-x assembler-with-cpp' to the gcc invocation (we know only gcc will be used to build libffi) somehow.  (You might think we could just use *.S but I think that is unreliable.  I've found in practice that sometimes the case of a file can seemingly randomly be
changed on NT at least.)

I would do this but as it turns out I don't immediately have a convenient way to test this.  Maybe eventually I'll build a cross toolchain to try it.  I'd rather someone who builds on the right sort of machine regularly do it though.

Tom
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-04-23 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 21:26 David.Billinghurst [this message]
2002-03-28 16:55 billingd

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=20010424041951.919.qmail@sourceware.cygnus.com \
    --to=david.billinghurst@riotinto.com \
    --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).