public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Gaurav Jain <gaurav.anywhere@gmail.com>
Cc: gcc-help@gcc.gnu.org, Jay <jayk123@hotmail.com>
Subject: Re: Error Compiling GCC on Solaris 10 / x86
Date: Sun, 03 Aug 2008 05:12:00 -0000	[thread overview]
Message-ID: <48953E03.A3955F01@dessent.net> (raw)
In-Reply-To: <42f6506e0808022127l3b5a961dgf8f9c62ed0459430@mail.gmail.com>

Gaurav Jain wrote:

> In fact, I specifically need to *try out* the GNU ld / GNU as
> combination to debug some issue in the binary

Oh.  That wasn't clear.

So, it looks like gcc is passing a -T option for a linker script that
the Solaris-provided GNU ld can't find.  Run the failing link command
with -### to see what the invocation of the linker is, and then figure
out if the linker script that gcc is passing exists, and if so where. 
If not, figure out why it's not included.  'elf_i386.xsc' should be the
variant for 32 bit shared libraries built with -z combreloc.  What
version is this /usr/sfw/bin/gld anyway?  If it's ancient it may be too
old for gcc 4.1.

> Even if it's not recommended, but I'm sure it sure does build fine
> with that combination?

I can't parse this.  Are you asking why GNU ld doesn't generally work
with Solaris 10?  It's because of a new type of shared library that GNU
ld doesn't yet support, as far as I can tell:
<http://sourceware.org/bugzilla/show_bug.cgi?id=1021>.  I don't know if
you can expect a gcc bootstrap to complete or not with GNU ld even if
you fix the missing linker script problem.

Brian

  reply	other threads:[~2008-08-03  5:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2008-08-03  6:23         ` Gaurav Jain
2008-08-02 14:59 Gaurav Jain
2008-08-02 17:02 ` Brian Dessent

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=48953E03.A3955F01@dessent.net \
    --to=brian@dessent.net \
    --cc=gaurav.anywhere@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jayk123@hotmail.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).