From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26888 invoked by alias); 9 Apr 2003 15:38:17 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 26868 invoked from network); 9 Apr 2003 15:38:17 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 9 Apr 2003 15:38:17 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h39FcHe04828 for ; Wed, 9 Apr 2003 11:38:17 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h39FcGJ02544; Wed, 9 Apr 2003 11:38:16 -0400 Received: from workshop.nickc.cambridge.redhat.com.redhat.com (vpn50-23.rdu.redhat.com [172.16.50.23]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h39Fc4m06870; Wed, 9 Apr 2003 11:38:12 -0400 To: robert_f_sharp@platts.com Cc: binutils@sources.redhat.com Subject: Re: ld core dump References: <85256D02.0062C3AC.00@corpnj148ls01.mcgraw-hill.com> From: Nick Clifton Date: Wed, 09 Apr 2003 15:38:00 -0000 In-Reply-To: <85256D02.0062C3AC.00@corpnj148ls01.mcgraw-hill.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-04/txt/msg00238.txt.bz2 Hi Robert, > luck. I have included the latest output. The one thing that attracts my > attention is the output, sparc, not as it should be, sparcv9. Is it trying to > link libnss_winbind.so as a 32bit (sparc?) oject? Probably. It sounds like you have a 32bit sparc targeted linker, so it is trying to create a 32bit sparc executable, and it gets rather confused when you give it 64bit libraries... I am not a sparc expert, so I am not sure whether there is a different linker to create 32bit and 64bit executable or just one linker and a command line switch. (Or maybe there is only one linker and the linker is supposed to be clever and work out which kind of binary it is supposed to create from its input files). > bash-2.05$ make > Using FLAGS = -O -m64 -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper Could you make "make" tell you the *exact* command line that it is executing ? It may be that there are some strange switches in there, or maybe a 32bit object file... Also could you add "-v" to the command line ? I assume that you are using gcc to drive the linker, so passing "-v" to gcc will cause it to print out the command line that it is using to invoke the linker Cheers Nick