Date:	Fri, 4 Jun 93 12:25:37 EDT
From:	DJ Delorie <dj AT ctron DOT com>
To:	xjzhu AT math DOT uwaterloo DOT ca
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: problems with djgpp1.10 (fwd)

> But at least in the file new110.doc, you should add gcc is now picky about
> file extensions. (gcc -x c++ is obsolete)

Gcc was always picky about file extensions.  You're right about
new110.doc.  1.10 has had a lot of ommision problems due to a tight
deadline.  1.11 should be more robust.

> What's the advantage of not allowing me to use test.c instead of test.cc?

That's up to the FSF, who made the change in gcc.c.  Gcc uses the
extension to determine how to compile the file.  Also, make uses the
extension to determine which commands to invoke for that file.  In all
cases, everything works smoother if you use the C++ extension.

> Why every time I have to type those lengthy  -lpc -lgpl while I am expecting
> the linker to do it for me? In a word, why make such a change from
> djgpp1.09 to djgpp1.10?

The -lpc was always required.  In 1.09, the GPL and non-GPL code was
mixed a bit, so it was hard for a developer to guarantee that none of
their application was GPL'd.  So, for 1.10, I put all the GPL code in
libgpl.a, so if you wanted GPL you had to link it in manually, and you
wouldn't get suprized by a lawyer someday if you didn't.

- Raw text -