public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Madore <mmadore@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] GLIBC __deregister_frame_pointer compiler error
Date: Thu, 27 Jul 2000 23:15:29 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205237@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205235@msgid-missing>

Hi Jim,

> 	While trying to compile glibc on the 2.4 kernel, I get the error messages
> 	included below.  On 2.3.99, everything compiles fine.  Any ideas where to
> 	look to solve this?
> 
> Something must have changed.  Just changing the kernel shouldn't cause a
> previously working build to fail.

I first tried building with 2.4 kernel and header files.  When that
failed, I replaced the 2.4 header files and kernel with 2.3.99.  After
restarting the machine, I was able to compile glibc.
 
> However, there is a known problem here.  glibc has a list of routines exported
> from libgcc.  This list contains gcc internal EH routines.  This list of EH
> routines is now different because of the IA-64 specific EH support.  If
> you delete these EH routines from the glibc export list, or if you add the
> new IA-64 specific routines, then this problem will go away.  Either way,
> you are making an ABI change, so this may require recompiling all libraries
> and applications linked against glibc.
> 
> The specific file to look at is csu/Versions, and look at section
> "Exception handling support functions from libgcc".

I tried removing this section and recompiling, but I still get the same
error message.  Do I need to alter anything else?

> I have only seen this problem show up when trying to link against C++ shared
> libraries.  Oh, I remember why, whether the problem shows up or not depends
> on which order you link in libgcc and glibc.  I don't remember which order
> it was that failed, but you can experiment.

I think if you link libc first you get the unresolved symbols.
 
Mike Madore




      parent reply	other threads:[~2000-07-27 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-27 19:35 [Linux-ia64] GLIBC __deregister_frame_pointer compiler error Michael Madore
2000-07-27 20:19 ` Jim Wilson
2000-07-27 23:08 ` Jim Wilson
2000-07-27 23:15 ` Michael Madore [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-105590678205237@msgid-missing \
    --to=mmadore@turbolinux.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