public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Installing gcc 4.7.2 on Solaris 10 - SPARC platform
Date: Sun, 16 Dec 2012 09:07:00 -0000	[thread overview]
Message-ID: <50CD8F38.30104@wippies.com> (raw)
In-Reply-To: <1355617904584-897964.post@n5.nabble.com>

16.12.2012 2:31, Holmes.Sherlock kirjoitti:
> 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/
> <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.

I built gcc-4.7.2 for sparc-solaris2.10 and i686-solaris2.10 targets on 
my laptop with
AMD Athlon64x2 TK-55 1.8 GHz and CentOS 6.3 Linux and it took about 15 
minutes
for each. The GNU Linux binutils 2.23.51.0.x was used for 'as' and 'ld' 
and such and
building them took about 5  minutes for each 
(sparc&sparc64/i686&x86_64).  No
problems at all with these.  Meaning during the builds...

But  what is the problem with using only the GNU binutils always? With 
cross GCCs
using GNU binutils is the only possibility, with native GCCs one can use 
also the native
Sun 'as', 'ld' and so on, but if the GNU ones really work, why one would 
use different
components on the native platform?

Generally I don't understand why anyone would use a platform where compiling
something takes over 8 hours as a development/build environment and not only
as a runtime platform...

  reply	other threads:[~2012-12-16  9:07 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 [this message]
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
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=50CD8F38.30104@wippies.com \
    --to=kai.ruottu@wippies.com \
    --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).