From: "Michael N. Filippov" <michael AT idisys DOT iae DOT nsk DOT su>
Newsgroups: comp.os.msdos.djgpp
Subject: GCC and long file names
Date: 6 Feb 2001 10:47:05 GMT
Lines: 44
Message-ID: <95okn9$rgo$1@news.itfs.nsk.su>
NNTP-Posting-Host: idisys.iae.nsk.su
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
X-Trace: news.itfs.nsk.su 981456425 28184 193.124.169.11 (6 Feb 2001 10:47:05 GMT)
X-Complaints-To: usenet AT news DOT itfs DOT nsk DOT su
NNTP-Posting-Date: 6 Feb 2001 10:47:05 GMT
User-Agent: tin/pre-1.4-19990517 ("Psychonaut") (UNIX) (Linux/2.4.0-test1 (i586))
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello !

I have DJGPP on computer with Win98. And cannot debug source files with long 
names. Example:
test$ cat long_long_long_source_file_name.cpp
#include <iostream>

int main(void)
{
  cout << "*** Start ***" << endl;
  return 0;
}

And if look into .o after compilation with debug information we can see
"long_long_long" (cut to 14 symbols). this is why it cannot be traced
in RHIDE for example: it just gives me
+-[_]----------- Error ----------------+
¦                                      ¦
¦  Could not find the source file      ¦
¦  long_long_long.                     ¦
¦                                      ¦
¦                                      ¦
¦                  OK   _              ¦
¦                ________              ¦
+--------------------------------------+

test$ gcc --version
2.952

But if i use GCC 2.952 on my Linux
idisys:~$ gcc --version
2.95.2

It stores entire file name in .o file.

What can I do ?

Sincerely,
Michael