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 15:48:00 -0000	[thread overview]
Message-ID: <ADE87C5A0ECCDD4F957C11445BD38CFD0115BDDE@MI8NYCMAIL02.Mi8.com> (raw)


> 
> > Yes. I cannot see why not...
> 
> Because GCC depends upon and applies certain transformations 
> to the header 
> files it was exposed to when built.  This may explain your problems.
OK, I am building a version of 3.2.3 without the sparcv9-sun-solaris2
set, and it seems like it is proceeding well. I am not sure what I
get out of this, but probably a 32 bit exe that can produce 64 bit
apps.

My bigger question is this:
1. I want a compiler that can build me 32 & 64 bit executables
on single box.
2. My base level support is Solaris 2.6
Can I even do this? 
Or ,
1. Do I need a version hosted on 2.6 for all 32 bits
2. A version hosted on a 64bit 2.7 (though it is 32 bit) 
for all 64 bit output?

I need to support 32 bits 2.6->2.9, 64 bits 2.7->2.9

BTW, I plan to use /usr/ccs/bin/as and /usr/ccs/bin/ld for all my needs.

thx!
balaji

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 15:48 Balaji Srinivasa [this message]
2004-03-19 16:28 ` 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 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  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=ADE87C5A0ECCDD4F957C11445BD38CFD0115BDDE@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).