public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: qiuhb <qiuhb@necas.nec.co.jp>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] make cross-gcc error about GNUPro ToolKit
Date: Mon, 21 May 2001 10:13:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005631@msgid-missing> (raw)

Hi

I want to get a cross-compile envionment using GNUPro ToolKit.
After I enter into /work/ia64 diretory and configure with
"../src/configure --target=ia64-pc-linux
--with-headers=/work/ia64/usr/include --with-libs=/work/ia64/usr/lib"
and type "make all install" and have a gcc tool,I make a file and some
errors happen as follows:

[root@qiuhb libiberty]# /usr/local/ia64-pc-linux/bin/gcc
/work/qhb/read.c
/usr/local/lib/gcc-lib/ia64-pc-linux/2.9-ia64-000216-final/../../../../ia64-pc-linux/bin/ld:
warning: ld-linux-ia64.so.2, needed by /lib/libc.so.0, not found (try
using --rpath)
/lib/libc.so.0: undefined reference to `_dl_debug_impcalls@@GLIBC_2.2'
/lib/libc.so.0: undefined reference to
`_dl_lookup_versioned_symbol@@GLIBC_2.2' /lib/libc.so.0: undefined
reference to `_dl_relocate_object@@GLIBC_2.2'
..
..
/lib/libc.so.0: undefined reference to `_dl_lookup_address@@GLIBC_2.2'
collect2: ld returned 1 exit status

I get a ld-linux-ia64.so.2 file from glibc-2.2-001117p1.ia64.rpm and
make again,but the error have no difference.
This error message exist in /work/ia64/ia64-pc-linux/libiberty as same
and dont create a Makefile.So many file have not make.

If who knows ,Please help me.

Thanks a lot.

Qiu HongBing.



             reply	other threads:[~2001-05-21 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 10:13 qiuhb [this message]
2001-05-21 20:02 ` [Linux-ia64] make cross-gcc error about GNUPro ToolKit Jim Wilson

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=marc-linux-ia64-105590693005631@msgid-missing \
    --to=qiuhb@necas.nec.co.jp \
    --cc=linux-ia64@vger.kernel.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