public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Anil Shinde <Anil.Shinde@xoriant.com>
To: "'epotter@eep.burdell.org'" <epotter@eep.burdell.org>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: RE: 64-bit gcc3.1 on Solaris?
Date: Fri, 19 Jul 2002 09:43:00 -0000	[thread overview]
Message-ID: <D1006BE5496ED411B95C00D0B77E65C4023BCFF5@sjnt003.xoriant.com> (raw)

Hi Elliott Potter,

You might want to take a look at this site, I came across this when I was
hunting for some information on building gcc on sparc /w solaris 8.

http://sunblade100.wells.org.uk/cache/65.html


Hope this helps.

-Anil

             reply	other threads:[~2002-07-19 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  9:43 Anil Shinde [this message]
     [not found] <616BE6A276E3714788D2AC35C40CD18D6BFBC9@whale.softwire.co.uk>
2002-07-01 11:23 ` Rupert Wood
2002-07-01 12:46   ` Elliott Potter
  -- strict thread matches above, loose matches on Subject: below --
2002-06-29 22:52 Elliott Potter

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=D1006BE5496ED411B95C00D0B77E65C4023BCFF5@sjnt003.xoriant.com \
    --to=anil.shinde@xoriant.com \
    --cc=epotter@eep.burdell.org \
    --cc=gcc-help@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).