public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Balaji Srinivasa" <Balaji@bladelogic.com>
To: "Eric Botcazou" <ebotcazou@libertysurf.fr>
Cc: gcc@gcc.gnu.org
Subject: RE: GCC 3.2.3 on Solaris 2.7
Date: Fri, 19 Mar 2004 21:40:00 -0000	[thread overview]
Message-ID: <ADE87C5A0ECCDD4F957C11445BD38CFD0B9C3B@MI8NYCMAIL02.Mi8.com> (raw)



> > 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


             reply	other threads:[~2004-03-19 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 21:40 Balaji Srinivasa [this message]
2004-03-19 22:18 ` Eric Botcazou
  -- strict thread matches above, loose matches on Subject: below --
2004-03-22 17:04 Balaji Srinivasa
2004-03-22 17:11 ` Eric Botcazou
2004-03-23  8:51   ` Toon Moene
2004-03-19 23:02 Balaji Srinivasa
2004-03-19 22:56 Balaji Srinivasa
2004-03-19 22:54 Balaji Srinivasa
2004-03-19 20:04 Balaji Srinivasa
2004-03-19 21:02 ` Eric Botcazou
2004-03-19 15:48 Balaji Srinivasa
2004-03-19 16:28 ` Eric Botcazou
2004-03-19  7:53 Balaji Srinivasa
2004-03-19  9:18 ` Eric Botcazou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ADE87C5A0ECCDD4F957C11445BD38CFD0B9C3B@MI8NYCMAIL02.Mi8.com \
    --to=balaji@bladelogic.com \
    --cc=ebotcazou@libertysurf.fr \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).