This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: GCC 3.2.3 on Solaris 2.7
- From: "Balaji Srinivasa" <Balaji at bladelogic dot com>
- To: "Eric Botcazou" <ebotcazou at libertysurf dot fr>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 19 Mar 2004 15:04:06 -0500
- Subject: RE: GCC 3.2.3 on Solaris 2.7
> > OK. This is what I also concluded. So I kicked of a build (twice)
> > and it churned for a while. It does not complete well.
>
> Which bootstrap compiler?
gcc 2.95.2 32 bit built on 2.5.1
>
> > ---------config.status------------
> > #!/bin/sh
>
> Nah :-) /bin/sh is not reliable as a configure shell. See the
> Solaris-specific release notes.
I am surprised. I am a bash user, and that is what it should be picking
up...
>
> > # This file was generated automatically by configure. Do not edit.
> > # This directory was configured as follows:
> > ../configure
> > --with-gcc-version-trigger=/home/balaji/gcc-3.2.3/gcc/version.c
> > --host=sparc-sun-solaris2.7 --prefix=/home/balaji/gcc-64
> > --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --disable-libgcj
> > --disable-nls --enable-languages=c,c++,objc --norecursion
> > # using "mh-frag"
>
> > gmake[4]: Entering directory
> >
> `/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/sparcv9
> /libiberty
> '
> > gmake[4]: *** No rule to make target `all'. Stop.
>
> Just to be sure: your Solaris 7 kernel is 64-bit capable, right?
Yes.
Here is more info:
1. Since it was past boostrap (i.e bootstrap was complete),
I decided that this failure might not be very bad.
2. I attempted an install, which went through all the steps
and failed at the same location.
3. However, the installed files seemed complete to me, so
I tried to build a few apps.
4. I built Python 2.1 for a 32 bit sample
5. I built lsof 4.70 for a 64 bit sample
6. They both built successfully and ran successfully.
I am thinking that these failures might be due to
(a) me setting --disable-libgcj
(b) me setting --enable-languages=c,c++,objc
and the building of the sparcv9 dirs.
This did not happen on 2 other 32 bit builds.
1. Solaris 2.6
2. Linux 2.4
I am in the process of building for AIX 4.3.3 which does
support 64 bit exe's, and it is going well so far.
To conclude, I am not sure what caused it, I am not sure
if I am only adding noise, but I will keep everyone posted
if I have progress.
In the meantime, if anyone can point me to something, it
will be great.
In the meantime, I thank Eric for his help.
thx
balaji