public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: "Holmes.Sherlock" <its.dipanjan.das@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Installing gcc 4.7.2 on Solaris 10 - SPARC platform
Date: Sun, 16 Dec 2012 21:51:00 -0000	[thread overview]
Message-ID: <fb8c575360f6.50cdfbe6@blastwave.org> (raw)
In-Reply-To: <1355617904584-897964.post@n5.nabble.com>


> Thanks *Dennis* for your assistance. However, I have been able to 
> compile gcc
> 4.7.2 on Solaris 10 (SPARC) without your gcc 4.5.1 pre-compiled binary
> package. Here is the precise steps I follwed in case someone else 
> needs it
> later:
> 
> 1. Installed gcc 3.4.6 pre-compile binary from  http://sunfreeware.com/
> <   which got installed /usr/local/bin/
> 2. Installed MPFR library under /usr/local: *./configure
> --prefix=/usr/local, make && make install*
> 3. Installed MPC library under /usr/local: *./configure --prefix=/usr/local,
> make && make install*
> 4. Installed GMP library under /usr/local: *./configure --prefix=/usr/local,
> make && make install*
> 5. Installed binutils-2.23.1 under /usr/local: *./configure
> --prefix=/usr/local, make && make install*
> 6. Set the environment variable to force gcc make process to use GNU as:
> AS=/usr/local/bin/as
> 7. Set the environment variable to force gcc make process to use GNU ld:
> AS=/usr/local/bin/ld
> 8. Started gcc build: *./configure --prefix=/usr/local, make && make
> install*
> 
> The build process ran over 8 hours (I don't know exactly how much time 
> it
> tiik as I left the office after 8 hours and found itself ready the next
> morning). I did the same process twice on the same machine and it got 
> built
> successfully both the times.

Success is measured via the testsuite so I would really like to know what sort of 
results you managed.  Please. 

> 
> P.S. Now I want to package my gcc 4.7.2 installation in phgadd format 
> so that if anybody else needs it, it can be installed without such pain. 
> Will you please help me in this regard?

I have extensive experience with this however I won't package nor aid in
the distribution of a thing which is untested. I have GCC 4.7.2 built over and 
over on Solaris and no way would I release them to the unsuspecting public 
without a reasonable public testsuite. 

Dennis 

  parent reply	other threads:[~2012-12-16 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 16:14 Dipanjan Das
2012-12-05 17:04 ` Dennis Clarke
2012-12-05 18:28   ` Holmes.Sherlock
2012-12-16  0:31     ` Holmes.Sherlock
2012-12-16  9:07       ` Kai Ruottu
2012-12-16  9:39         ` Holmes.Sherlock
2012-12-16 21:45           ` Dennis Clarke
2012-12-17  0:04             ` Holmes.Sherlock
2012-12-16 21:51       ` Dennis Clarke [this message]
2012-12-17  0:09         ` Holmes.Sherlock
2012-12-17  0:43           ` Dennis Clarke
2012-12-17  0:59             ` Holmes.Sherlock
2012-12-17 17:40       ` Tom Christensen
2012-12-17 17:49         ` Dennis Clarke

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=fb8c575360f6.50cdfbe6@blastwave.org \
    --to=dclarke@blastwave.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=its.dipanjan.das@gmail.com \
    /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).