public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: robert_f_sharp@platts.com
Cc: binutils@sources.redhat.com
Subject: Re: ld core dump
Date: Tue, 08 Apr 2003 15:31:00 -0000	[thread overview]
Message-ID: <m3u1d9ropd.fsf@workshop.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <85256CFD.006681D6.00@corpnj148ls01.mcgraw-hill.com>

Hi Robert,

> bash-2.05$ /usr/local/tools/binutils/bin/as -v
> GNU assembler version 2.13.2.1 (sparc-sun-solaris2.9) using BFD version 2.13.2.1
> 
> Compiling nsswitch/wb_common.c with -fPIC
> Compiling nsswitch/winbind_nss_solaris.c with -fPIC
> Linking nsswitch/libnss_winbind.so
> collect2: ld terminated with signal 11 [Segmentation Fault]
> /usr/local/tools/binutils/bin/ld: warning: sparc:v9 architecture of input file
> `nsswitch/winbind_nss.po' is incompatible with sparc output
> /usr/local/tools/binutils/bin/ld: warning: sparc:v9 architecture of input file
> `nsswitch/wb_common.po' is incompatible with sparc output
> /usr/local/tools/binutils/bin/ld: warning: sparc:v9 architecture of input file
> `nsswitch/winbind_nss_solaris.po' is incompatible with sparc output
> make: *** [nsswitch/libnss_winbind.so] Error 1
> 
> ld core dumps and does not go any futher, have I supplied enough info, anybody
> have an idea why ld core dumps?

Sorry - there is not really enough information to go on here.

Do you know why the linker is complaining about the architecture
mismatches ?  (This may be at the root of the bug).  ie are the input
files really 'sparcv9' and is the output file really 'sparc' ?

Are you able to reduce the problem to a small, reproducible test case?

What is the complete command line that you are using ?

Cheers
        Nick



  reply	other threads:[~2003-04-08 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 18:44 robert_f_sharp
2003-04-08 15:31 ` Nick Clifton [this message]
2003-04-08 18:04 robert_f_sharp
2003-04-09 15:38 ` Nick Clifton
2003-04-10 18:03 robert_f_sharp

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=m3u1d9ropd.fsf@workshop.nickc.cambridge.redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=robert_f_sharp@platts.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).