From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: Re: Make and filename case Date: Tue, 18 Apr 2000 17:38:46 +0400 Organization: MTU-Intel ISP Lines: 33 Message-ID: <38FC6566.964A6265@mtu-net.ru> References: NNTP-Posting-Host: ppp103-164.dialup.mtu-net.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Trace: gavrilo.mtu.ru 956069913 18329 212.188.103.164 (18 Apr 2000 14:58:33 GMT) X-Complaints-To: usenet-abuse AT mtu DOT ru NNTP-Posting-Date: 18 Apr 2000 14:58:33 GMT X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en,ru To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Sure, for example, GCC treats .c and .C differently. I've had this problem before. GCC simply generated a bit different code depending on the case. .c is C but .C is C++. This is because GCC has com from Unix which takes care about the case. :) You may have the same problem here. -- Alexei A. Frounze ----------------------------------------- Homepage: http://alexfru.chat.ru Mirror: http://members.xoom.com/alexfru Eli Zaretskii 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.