From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Lance Taylor <ian@cygnus.com>
To: dj@stealth.ctron.com, Gordon Hogenson <ghogenso@u.washington.edu>
Cc: gas2@cygnus.com
Subject: Re: [ghogenso@u.washington.edu: Problems with .cpp extension: minor annoyances]
Date: Wed, 28 Sep 1994 08:33:00 -0000
Message-id: <199409281533.LAA19725@sanguine.cygnus.com>
References: <9409281141.AA06727@delorie>
X-SW-Source: 1994/msg00116.html

   Date: Wed, 28 Sep 94 07:41:21 -0400
   From: dj@stealth.ctron.com (DJ Delorie)

   Is this the desired behavior?  gcc *does* support a lot of file
   extensions for each language.

   Date: Tue, 27 Sep 1994 10:25:42 -0700 (PDT)
   From: Gordon Hogenson <ghogenso@u.washington.edu>

   There are a few problems with the .cpp filename extension under
   DJGPP.  It seems that the various utility programs don't
   deal well with it.  ld reports errors with the wrong filename
   extension -- always 'foo.cc' even if the file is really 'foo.cpp'.

   It doesn't seem to be a serious problem with errors and warnings
   from ld, since I can easily tell what is meant [although I suppose
   editors that rely on this to locate a position in a source file will not
   work], but I find that GDB can't find the source files.
   It looks for 'foo.cc' when it should be looking for 'foo.cpp'.

There is nothing about file extensions in either ld or gdb.  Both
programs get the filenames out of the debugging information.  I
suspect that if you examine the debugging information in your .o file,
you will find that it refers to foo.cc, not foo.cpp.  I suspect
further that your foo.cpp file includes # directives naming the file
foo.cc.

If not, then there is a bug.  Please provide a testcase showing the
problem.

Ian