This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
bootstrap/9451: Cannot build cross gcc /w shared libs
- From: thomas dot koeller at baslerweb dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 27 Jan 2003 15:33:21 -0000
- Subject: bootstrap/9451: Cannot build cross gcc /w shared libs
- Reply-to: thomas dot koeller at baslerweb dot com
>Number: 9451
>Category: bootstrap
>Synopsis: Cannot build cross gcc /w shared libs
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: support
>Submitter-Id: net
>Arrival-Date: Mon Jan 27 15:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Thomas Koeller
>Release: gcc-3.2.1
>Organization:
>Environment:
Host: i686-pc-linux-gnu
Target: powerpc-unknown-linux-gnu
>Description:
I am trying to configure and build a cross compiler for a powerpc-unknown-linux-gnu target to run on a i686-pc-linux-gnu host. The target C library is glibc-2.3.1, built as a shared library. The build process fails when it comes to building libgcc. The error message I get is about being unable to read symbol information from /lib/libc.so, and so I looked at the Makefile and found that it attempts to link libgcc with libc. It does this by defining SHLIB_LC as '-lc'. When I redefine SHLIB_LC as an empty string, the problem goes away. I do not quite understand why libgcc would be linked against libc at this stage.
I also noticed that the compiler invokes collect2 to link libgcc, even though I am using GNU ld (and specified -with-gnu-ld as a configure argument). I always assumed collect2 was only required to overcome deficiencies in non-GNU linkers?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: