This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: make install fails
Phil Edwards writes:
> On Sat, Jul 05, 2003 at 11:47:41PM -0400, Jerry Quinn wrote:
> > I wish. During the configure, I'm seeing:
> >
> > checking for install location... $(prefix)/include/c++/3.3
> >
> > libstdc++-v3/config.status contains:
> >
> > /home/jlquinn/gcc/dev/gcc/libstdc++-v3/configure --cache-file=../config.cache --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --enable-multilib --program-suffix=dev --with-system-zlib --enable-threads --with-cpu=athlon --enable-langs=c,c++,f77,java --with-gcc-version-trigger=/home/jlquinn/gcc/dev/gcc/gcc/version.c --srcdir=../../../gcc/libstdc++-v3 --with-target-subdir=i686-pc-linux-gnu
> >
> > config.h is getting:
> >
> > #define VERSION "3.3"
> >
> > I really don't know config well enough to track what's going on.
>
> The version number string comes from the compiler, via gcc/version.c.
> The library doesn't actually store the "3.x" string anywhere.
Does the configury attempt to get the version string from running a
compiler? If so, it would make sense if paths were wrong.
gcc/version.c contains:
#include "ansidecl.h"
#include "version.h"
/* This is the string reported as the version number by all components
of the compiler. If you distribute a modified version of GCC,
please modify this string to indicate that, e.g. by putting your
organization's name in parentheses at the end of the string. */
const char version_string[] = "3.4 20030706 (experimental)";
/* This is the location of the online document giving instructions for
reporting bugs. If you distribute a modified version of GCC,
please change this to refer to a document giving instructions for
reporting bugs to you, not us. (You are of course welcome to
forward us bugs reported to you, if you determine that they are
not bugs in your modifications.) */
const char bug_report_url[] = "<URL:http://gcc.gnu.org/bugs.html>";