Message-ID: <35167571.33220523@cs.joensuu.fi> Date: Mon, 23 Mar 1998 16:45:05 +0200 From: Eugene Ageenko MIME-Version: 1.0 To: bug-gcc AT prep DOT ai DOT mit DOT edu, djgpp AT delorie DOT com Subject: Problems with GCC 2.8.0 Content-Type: multipart/mixed; boundary="------------CFD26D344AFAB55498A5D158" Precedence: bulk This is a multi-part message in MIME format. --------------CFD26D344AFAB55498A5D158 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit I am C programmer and use DJGPP to compile my programs for 32-bit DOS. Few days ago I downloaded the new distribution of DJGPP consisting of GCC 2.8.0 (formerly I used 2.7.2). (I delete all old files and install all new) I wish report that I have some problems with this new GCC compiler that could be possibly BUGS in this. (1) First, is that GCC does not want to compile the program having more than one module, let say test.c and module.c following way: >gcc test.c module.c -o test It was working with gcc 2.7.2 (for DOS and for Solaris) It is also working Ok. currently following way: >gcc -c test.c >gcc -c module.c >gcc test.o module.o -o test or this way >gcc -c module.c >gcc test.c module.o -o test So the problem is likely that it does not want to compile multiple .c files in one command line. Here are included those test files: test.c, module.c, module.h They are to simple. (2) The second problem is concerning the long names under Win95. The problem is that GCC does not want to compile programs of their names typed in Uppercase. The following command does not cause any errors: >gcc -c test.c But following command results in error: >gcc -c TEST.C gcc.exe: installation problem, cannot exec `cc1plus': No such file or directory (ENOENT) I understand that gcc is not caseinsensitive and that it treats .C files as the C++ files, but what about cc1plus then? Where it is from? Interesting that even +LFN set to "n" in my env file, GCC still think that test.c and test.C are different because the extension. Unfortunately my shell type the names in CAPITAL letters that causes the problem. Reagrds: Eugene Ageenko. Please reply me by e-mail, since I am not member of mail-list. ageson AT cs DOT joensuu DOT fi --------------CFD26D344AFAB55498A5D158 Content-Type: text/plain; charset=koi8-r; name="test.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="test.c" /* test program that does not compiled with gcc 2.8.0 following way */ /* gcc test.c module.c -o test.exe */ #include "module.h" #include int main(void) { hello(); exit(0); } --------------CFD26D344AFAB55498A5D158 Content-Type: text/plain; charset=koi8-r; name="module.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="module.c" #include "module.h" #include int hello(void) { printf("Hello World"); } --------------CFD26D344AFAB55498A5D158 Content-Type: text/plain; charset=koi8-r; name="module.h" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="module.h" #ifndef __MODULE_H #define __MODULE_H int hello(void); #endif /* __MODULE_H */ --------------CFD26D344AFAB55498A5D158--