From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6900 invoked by alias); 1 Aug 2002 21:27:50 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 6891 invoked from network); 1 Aug 2002 21:27:49 -0000 Received: from unknown (HELO mail1.utc.com) (192.249.46.37) by sources.redhat.com with SMTP; 1 Aug 2002 21:27:49 -0000 Received: (from uucp@localhost) by mail1.utc.com (8.10.0/8.10.0) id g71LRmY27124 for ; Thu, 1 Aug 2002 17:27:48 -0400 (EDT) Received: from uusnwa08.utc.com(159.82.80.244) by mail1.utc.com via csmap (V6.0) id srcAAAtuaa_0; Thu, 1 Aug 02 17:27:48 -0400 Received: from ronbo.sikorsky.com (ronbo.sikorsky.com [140.76.12.150]) by uusnwa08.utc.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g71LRjV12421 for ; Thu, 1 Aug 2002 17:27:45 -0400 (EDT) Received: (from s29299@localhost) by ronbo.sikorsky.com (8.11.6+Sun/8.11.6) id g71LRhm06032 for gcc-help@gcc.gnu.org; Thu, 1 Aug 2002 17:27:43 -0400 (EDT) X-Authentication-Warning: ronbo.sikorsky.com: s29299 set sender to rmccall@sikorsky.com using -f Date: Thu, 01 Aug 2002 14:27:00 -0000 From: Ron McCall To: GCC Help Mailing List Subject: Problem building Solaris hosted PowerPC EABI cross compiler Message-ID: <20020801172743.A5998@sikorsky.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-SW-Source: 2002-08/txt/msg00003.txt.bz2 Hi, I am having trouble building a powerpc-eabi targeted cross compiler on my Sun Ultra 60 running Solaris 8. I have read through a couple of cross-GCC FAQs and through the GCC installation instructions but am having no luck. I am using native GCC (version 2.95.3) to build the cross compiler. I have done a fair amount of web searching on the error messages that I am getting but I haven't been able to find a solution. I have also tried a lot of different combinations of different versions of binutils and gcc trying to determine if the problem was with the latest versions (I even tried the exact versions mentioned in the FAQ below). Following the cross-GCC FAQ at the below URL (and substituting newer version numbers for all components, changing the target to powerpc-eabi and changing prefix to /opt/gcc-ppc-3.1.1), I have built and installed binutils 2.12.1, built and installed a bootstrap GCC 3.1.1 and built and installed newlib 1.10.0. I am running into problems building the full GCC. http://crossgcc.billgatliff.com/crossgccfaq/t1.html I wiped out the GCC build directory prior to re-configuring. This seems to be needed but isn't explicitly stated in the FAQ. Configuration succeeds but the following make does not. It dies while "Configuring in powerpc-eabi/libiberty" saying that: checking whether the C compiler (/export/home0/software/build/build-gcc/gcc/xgcc -B/export/home0/software/build/build-gcc/gcc/ -B/opt/gcc-ppc-3.1.1/powerpc-eabi/bin/ -B/opt/gcc-ppc-3.1.1/powerpc-eabi/lib/ -isystem /opt/gcc-ppc-3.1.1/powerpc-eabi/include -g -O2 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [configure-target-libiberty] Error 1 Inspecting config.log in powerpc-eabi/libiberty reveals the following error: configure:2212: /export/home0/software/build/build-gcc/gcc/xgcc -B/export/home0/software/build/build-gcc/gcc/ -B/opt/gcc-ppc-3.1.1/powerpc-eabi/bin/ -B/opt/gcc-ppc-3.1.1/powerpc-eabi/lib/ -isystem /opt/gcc-ppc-3.1.1/powerpc-eabi/include -o conftest -g -O2 conftest.c 1>&5 /opt/gcc-ppc-3.1.1/powerpc-eabi/bin/ld: warning: cannot find entry symbol _start; defaulting to 01800074 /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o): In function `__eabi': /export/home0/software/build/build-gcc/gcc/eabi.S:232: undefined reference to `__init' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:146: undefined reference to `__SDATA_START__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:148: undefined reference to `__SBSS_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:150: undefined reference to `__SDATA2_START__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:151: undefined reference to `__SBSS2_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:152: undefined reference to `__GOT_START__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:155: undefined reference to `__GOT_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:156: undefined reference to `__GOT2_START__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:157: undefined reference to `__GOT2_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:158: undefined reference to `__FIXUP_START__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:159: undefined reference to `__FIXUP_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:163: undefined reference to `__CTOR_LIST__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:164: undefined reference to `__CTOR_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:165: undefined reference to `__DTOR_LIST__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:166: undefined reference to `__DTOR_END__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:167: undefined reference to `__EXCEPT_START__' /export/home0/software/build/build-gcc/gcc/libgcc.a(eabi.o):/export/home0/software/build/build-gcc/gcc/eabi.S:171: undefined reference to `__EXCEPT_END__' collect2: ld returned 1 exit status configure: failed program was: #line 2207 "configure" #include "confdefs.h" main(){return(0);} These undefined symbols sound like ld script symbols to me (not knowing a whole lot) and also sort of C++ related (constructors, destructors, exceptions). Does anyone happen to know what I am doing wrong? I re-executed that failed xgcc command with a -v so I could see all the various tool invocations and don't see anything more there that would seem to help. If you need to see that too, let me know and I'll post it. Thanks for the help! -- Ron McCall Sikorsky Aircraft 203-386-4695 rmccall@sikorsky.com