public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: thomas.koeller@baslerweb.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/9451: Cannot build cross gcc /w shared libs
Date: Mon, 27 Jan 2003 15:36:00 -0000	[thread overview]
Message-ID: <20030127153321.25338.qmail@sources.redhat.com> (raw)


>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:


             reply	other threads:[~2003-01-27 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 15:36 thomas.koeller [this message]
2003-05-14 19:06 Dara Hazeghi
2003-05-17  6:58 giovannibajo

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=20030127153321.25338.qmail@sources.redhat.com \
    --to=thomas.koeller@baslerweb.com \
    --cc=gcc-gnats@gcc.gnu.org \
    /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).