This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6672: <fstream> header produces errors
- From: paolo at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, paolo at gcc dot gnu dot org, strieder at informatik dot uni-kl dot de
- Date: 16 May 2002 13:41:17 -0000
- Subject: Re: libstdc++/6672: <fstream> header produces errors
- Reply-to: paolo at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, paolo at gcc dot gnu dot org, strieder at informatik dot uni-kl dot de, gcc-gnats at gcc dot gnu dot org
Synopsis: <fstream> header produces errors
State-Changed-From-To: feedback->analyzed
State-Changed-By: paolo
State-Changed-When: Thu May 16 06:41:15 2002
State-Changed-Why:
Submitter provided the following feedback. For the time being I will keep the PR open, however, since I agree that at least a note should be added to the installation instructions.
////////
Hi paolo,
indeed, it is the same problem as reported by Maurizio Loreti.
And the solution is so easy. The problem is caused by an installation error.
It is not possible (not any more?) to install different gcc releases into the
same directory. I have done this for years without problems. Obviously some
header files have been moved without renaming. Old versions of some header
files remained at places occurring earlier in the search path, so are
preferred to the right ones for a given release. The result is mindbogging.
At least I was not the only one to get trapped.
Some analysis and suggestions to the long-standing cause:
Why are big parts of a gcc installation divided by the release numbers, while
other important parts are not. E.g. $PREFIX/lib/gcc-lib/i686-pc-linux-gnu/
contains a directory for each and every release. Why couldn't the same
strategy be adopted for the headers under $PREFIX/include?
Since linking statically is not too frequently done, the same problem with
statical libraries is unlikely to become a problem.
It should be avoided to install files under the same place and name under
$PREFIX whenever crucial changes have happened, e.g. moving other files. The
strategies are already there.
This should be enough to close my bug report. It should be warned against
installing different libstdc++ releases under the same $PREFIX. It doesn't
work in general with gcc-3.1.
Bernd Strieder
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6672