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: Mon, 22 Mar 2004 17:04:00 -0000	[thread overview]
Message-ID: <ADE87C5A0ECCDD4F957C11445BD38CFD0115BDEA@MI8NYCMAIL02.Mi8.com> (raw)

> 
> > 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.
> 
> Nice!
> 
> > 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.
> 
> No, I don't think so, these are common and well-tested 
> options.  I'd tend to 
> think of a shell problem if you used /bin/sh, such problems are very 
> frequent on Solaris.
> 
> > This did not happen on 2 other 32 bit builds.
> > 1. Solaris 2.6
> > 2. Linux 2.4
> 
> Sure, sparc-sun-solaris2.6 is not multilibed.
I think the shell was the problem. In fact, the documentation
should state that CONFIG_SHELL should always be exported, or,
configure should take the SHELL value from the env.

After that was set, a complete rebuild was successful.

However, config.status still shows #!/bin/sh whatever is set.

thx to Eric,
balaji

             reply	other threads:[~2004-03-22 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 17:04 Balaji Srinivasa [this message]
2004-03-22 17:11 ` Eric Botcazou
2004-03-23  8:51   ` Toon Moene
  -- strict thread matches above, loose matches on Subject: below --
2004-03-19 23:02 Balaji Srinivasa
2004-03-19 22:56 Balaji Srinivasa
2004-03-19 22:54 Balaji Srinivasa
2004-03-19 21:40 Balaji Srinivasa
2004-03-19 22:18 ` Eric Botcazou
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=ADE87C5A0ECCDD4F957C11445BD38CFD0115BDEA@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).