Mail Archives: djgpp/1998/03/22/08:05:10
On 21 Mar 1998, FWarren574 wrote:
> What I finally ended up doing was installing 2.7.1 on my system and
> then installing 2.8.0 over the top. This seems to work, but it was
> not obvious.
If GCC 2.8.0 didn't work unless you installed 2.7.x first, it might
mean that your current installation makes 2.8.0 use some files from
2.7.x. This is a Bad Thing, since these two versions are incompatible
enough to cause some subtle bugs in the long run.
Please report the problems you had when you installed 2.8.0 from
scratch, without a previous 2.7.x installation. This is how it's
supposed to work, so the problems you saw might be either bugs in the
ported GCC (which should be corrected ASAP), or some local snafu due
to how your system is configured. Either way, please report any such
problems, as we cannot correct them without detailed description.
> I found that the gpp.zip file in 2.8.0 has a file g++.exe (not a
> legal file name and it is there for sure).
It is there for Windows 9X users, where g++.exe is a valid name. If
you use a friendly unzip program (as opposed to PKUNZIP), it will
rename that file to g__.exe or something like that. Otherwise, you
get a warning but no real problem.
> I also noticed that there seemed to be missing include files in the new
> lgpplib280b. When I did a clean install, I was shorted a whole
> bunch of normal includes. When I extracted the 2.7.1 library and
> then overwrote it with 2.8.0, I ended up with everything.
Please report the missing include files. I'm not sure this is a real
problem, but without seeing the file names it is hard to know.
> I finally got the compiler running with this approach, but it is still giving
> me some complaints about templates.
This might be due to the fact that you are currently mixing files from
2.8.0 and 2.7.x. The right thing to do would be to install 2.8.0 from
scratch, and fix any problems you have after that, without using files
from 2.7.x.
- Raw text -