From: robert_f_sharp@platts.com
To: binutils@sources.redhat.com
Subject: ld core dump
Date: Thu, 03 Apr 2003 18:44:00 -0000 [thread overview]
Message-ID: <85256CFD.006681D6.00@corpnj148ls01.mcgraw-hill.com> (raw)
I have a problem when I try build samba in 64bit mode. It builds ok in 32bit.
The problem arises when linking nsswitch/libnss_winbind.so
On Solaris 9 I'm using
bash-2.05$ /usr/local/tools/gcc/bin/gcc -v
Reading specs from
/usr/local/tools/gcc/lib/gcc-lib/sparc-sun-solaris2.9/3.2.2/specs
Configured with: ../configure --with-as=/usr/local/tools/binutils/bin/as
--with-ld=/usr/local/tools/binutils/bin/ld --with-gnu-as --with-gnu-ld
--disable-nls --enable-languages=c,c++ --prefix=/usr/local/tools/gcc
Thread model: posix
gcc version 3.2.2
bash-2.05$ /usr/local/tools/binutils/bin/ld -v
GNU ld version 2.13.2.1
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?
Robert S.
next reply other threads:[~2003-04-03 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 18:44 robert_f_sharp [this message]
2003-04-08 15:31 ` Nick Clifton
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=85256CFD.006681D6.00@corpnj148ls01.mcgraw-hill.com \
--to=robert_f_sharp@platts.com \
--cc=binutils@sources.redhat.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).