From: Brian Dessent <brian@dessent.net>
To: Gaurav Jain <gaurav.anywhere@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error Compiling GCC on Solaris 10 / x86
Date: Sat, 02 Aug 2008 17:02:00 -0000 [thread overview]
Message-ID: <4894931C.FDF892C1@dessent.net> (raw)
In-Reply-To: <42f6506e0808020759qa4d7022xcecf10e7bbeab020@mail.gmail.com>
Gaurav Jain wrote:
> The configuration options I've used are:
> ./configure
I recommend you follow the advice of the installation instructions and
build in a separate directory outside of the source directory.
> The bootstrap compiler being used is GCC 3.4.3, configured using GNU
> as and Sun ld.
If you're using the Sun linker then you shouldn't also be telling gcc
that you're using the GNU linker, i.e. remove --with-gnu-ld.
Brian
next prev parent reply other threads:[~2008-08-02 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 14:59 Gaurav Jain
2008-08-02 17:02 ` Brian Dessent [this message]
[not found] <1217689174.6455.ezmlm@gcc.gnu.org>
2008-08-03 3:38 ` Jay
2008-08-03 3:54 ` Brian Dessent
2008-08-03 4:28 ` Gaurav Jain
2008-08-03 5:12 ` Brian Dessent
2008-08-03 6:23 ` Gaurav Jain
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=4894931C.FDF892C1@dessent.net \
--to=brian@dessent.net \
--cc=gaurav.anywhere@gmail.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).