This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: problem compiling gcc 2.9.5
- To: Jeffrey A Law <law at cygnus dot com>
- Subject: Re: problem compiling gcc 2.9.5
- From: Bryan Weston <bryanw at bluemoon dot sps dot mot dot com>
- Date: Wed, 4 Aug 1999 12:23:44 -0500 (CDT)
- cc: gcc-bugs at gcc dot gnu dot org
I don't know what to tell you. I had deleted the old directory, so I
unziped the source again, ran configure again and this time it works. The
only idea I have is that the shell I ran in first had some old variables
or something.
I have not finished the compile, but it is much further. I ran out of disk
space so I started over without -g.
Thanks for your help.
---
Bryan
On Tue, 3 Aug 1999, Jeffrey A Law wrote:
>
> In message <Pine.GSO.4.10.9908031000410.17802-100000@bluemoon>you write:
> >
> > I am trying to compile gcc 2.9.5, on Solaris 2.6 and I get the following
> > error.
> >
> >
> > bryanw@bluemoon: /tmp/a/gcc-2.95
> > 78 % make bootstrap
> > gnumake[1]: Entering directory `/tmp/a/gcc-2.95/libiberty'
> > test x"yes" != xyes || \
> > gcc -c -DHAVE_CONFIG_H -g -I. -I./../include `case "-g -g -O2
> > -fno-implicit-templates" in *-fpic* ) echo -fpic ;; * ) echo -fPIC ;;
> > esac` vsprintf.c -o pic/vsprintf.o
> > vsprintf.c: In function `vsprintf':
> > vsprintf.c:47: `_IOSTRG' undeclared (first use in this function)
> > vsprintf.c:47: (Each undeclared identifier is reported only once
> > vsprintf.c:47: for each function it appears in.)
> > gnumake[1]: *** [vsprintf.o] Error 1
> > gnumake[1]: Leaving directory `/tmp/a/gcc-2.95/libiberty'
> > gnumake: *** [all-libiberty] Error 2
> >
> >
> > I looked everywhere but could not find a definition for _IOSTRG. I am
> > compiling with egcs 1.1.2, but also tried with gcc 2.8.1.
> I believe solaris already has an implementation of vsprintf, so you should
> look into why the configure code in libiberty choose to try and build
> vsprintf in the first place.
>
> You can probably find a log of the libiberty configure process by looking for
> a file called config.log in the libiberty directory.
>
> jeff
>
>