public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@ge.com>
To: <gcc-help@gcc.gnu.org>
Subject: RE: Compiling gcc 4.2.3 in Solaris 10
Date: Tue, 29 Jul 2008 21:47:00 -0000	[thread overview]
Message-ID: <8E460D1B58F94945A20AA70D4D41430D052DEADD@ALPMLVEM08.e2k.ad.ge.com> (raw)
In-Reply-To: <m3r69c3grd.fsf@google.com>

Hi All

> /cots/gnu/gcc-4.2.3/host-sparc-sun-solaris2.10/gcc/xgcc -B/cots/gnu/gcc-4.2.3/host-sparc-sun-solaris2.10/gcc/ -B/usr/local/sparc-sun-solaris2.10/bin/ -B/usr/local/sparc-sun-solaris2.10/lib/ -isystem /usr/local/sparc-sun-solaris2.10/include -isystem /usr/local/sparc-sun-solaris2.10/sys-include  -c -o crt1.o -x assembler-with-cpp ../.././gcc/config/sparc/sol2-c1.asm
>
> xgcc: error trying to exec '/usr/local/sparc-sun-solaris2.10/bin': execv: Permission denied
> make[3]: *** [crt1.o] Error 1
> make[3]: Leaving directory `/cots/gnu/gcc-4.2.3/host-sparc-sun-solaris2.10/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory `/cots/gnu/gcc-4.2.3'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/cots/gnu/gcc-4.2.3'
> make: *** [bootstrap] Error 2
>
> Any ideas or pointers?
Still do not know what may have been the problem. However, I cleaned out the gcc-4.2.3 directory, cleaned out /usr/local/sparc-sun-solaris2.10. I then recopied both and it worked fine thereafter. Thanks for all the input. Have not yet completed the compile but it has gone past this and is now in stage-3.

With Regards

Vardhan 

  reply	other threads:[~2008-07-29 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 16:38 Vardhan, Sundara (GE Infra, Energy)
2008-07-29 15:06 ` Ian Lance Taylor
2008-07-29 21:47   ` Vardhan, Sundara (GE Infra, Energy) [this message]
2008-07-30  2:41     ` 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=8E460D1B58F94945A20AA70D4D41430D052DEADD@ALPMLVEM08.e2k.ad.ge.com \
    --to=sundara.vardhan@ge.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).