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 [thread overview]
Message-ID: <199409281533.LAA19725@sanguine.cygnus.com> (raw)
In-Reply-To: <9409281141.AA06727@delorie>
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
next prev parent reply other threads:[~1994-09-28 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-09-28 4:39 DJ Delorie
1994-09-28 8:33 ` Ian Lance Taylor [this message]
1994-09-28 19:07 ` [ghogenso@u.washington.edu: Problems with .cpp extension] Gordon Hogenson
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=199409281533.LAA19725@sanguine.cygnus.com \
--to=ian@cygnus.com \
--cc=dj@stealth.ctron.com \
--cc=gas2@cygnus.com \
--cc=ghogenso@u.washington.edu \
/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).