Date:	Thu, 20 Apr 2000 13:01:08 -0400 (EDT)
Message-Id:	<200004201701.NAA16177@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<bv1ufs0h7pe6of4djpc3b13101u144dbg6@4ax.com> (message from Damian
	Yerrick on Thu, 20 Apr 2000 13:41:20 GMT)
Subject:	Re: Make and filename case
References:	<8dg7gh$smr$1 AT nnrp1 DOT deja DOT com> <Pine DOT SUN DOT 3 DOT 91 DOT 1000418112837 DOT 28255N-100000 AT is> <bv1ufs0h7pe6of4djpc3b13101u144dbg6 AT 4ax DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: Damian Yerrick <Bullcr_pd_yerrick AT hotmail DOT comRemoveBullcr_p>
> Newsgroups: comp.os.msdos.djgpp
> 
> On Tue, 18 Apr 2000 11:28:55 +0200 (IST), Eli Zaretskii
> <eliz AT is DOT elta DOT co DOT il> wrote:
> 
> >On Mon, 17 Apr 2000, Rossz wrote:
> >
> >> %.o: %.s
> >> 	$(AS) $*.s -o $*.o
> >> 
> >> I found if the filename has an extension of .S (big letter) instead of
> >> .s, this rule is not used.  On DOS/Windows systems, it should ignore the
> >> case when checking rules, in my opinion.
> >
> >If the rule says ".s", then why does the file have a .S extension?  .S
> >is interpreted by GCC differently than .s (see section 8.5 of FAQ for
> >details).
> >
> >You could simply rename the file to have a .s extension, that should
> >solve the problem.
> 
> That wouldn't work in plain DOS, where renaming the file to lowercase
> doesn't do a thing, as DOS's canonicalizer uppercases all filenames.

On DOS this problem couldn't exist at all, since when LFN is not
available, Make itself downcases all file names, and will only see *.s
files, with a lower-case .s.

The original problem, as stated, could only happen on a Windows
system, where a rename I suggested *will* work.

- Raw text -