From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc 3.0 questions.
Date: Sat, 10 Nov 2001 01:01:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805462@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805456@msgid-missing>
> error while loading shared libraries: /home/jholly/lib/libgcc_s.so.1:
> undefined symbol: __ia64_app_header
This can happen when you try to link together code from incompatible gcc
versions. One of the libraries somewhere that you are linking against was
compiled by the wrong compiler.
ia64_app_header was a variable that was present from about Oct 2000 to
June 2001 in the gcc start files (crtbegin.o). It never appeared in any
Trillian compiler release. It did appear in gcc 3.0. It was removed before
gcc-3.0.1. Note in particular that gcc 3.0 is not compatible with 3.0.1,
and 3.0.1 is not compatible with 3.0.2 for a different reason.
>I'm doing this using NUE and the tarball put together by Stephane Eranian
>and running it on my RH 7.1 box.
My guess is that Stephane's tarball was built using 3.0, and that you are
building your application with either 3.0.1 or 3.0.2. That won't work.
Either everything has to be compiled by 3.0, or everything has to be
compiled by 3.0.1, or everything has to be compiled by 3.0.2. By the
way, 3.0 won't build glibc, so that one isn't an option.
You can try replacing the file /home/jholly/lib/libgcc_s.so.1 with the
equivalent file from a gcc 3.0.[12] build. That might be enough to solve
your problem. It would be better to have a complete build with everything
compiled by the same gcc version.
Jim
prev parent reply other threads:[~2001-11-10 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 17:54 [Linux-ia64] gcc 3.0 questions Jim Hollenback
2001-11-10 1:01 ` Jim Wilson [this message]
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-105590698805462@msgid-missing \
--to=wilson@cygnus.com \
--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