public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* gcc 2.8.0/egcs and glibc 2
@ 1997-12-11 19:51 H.J. Lu
  1997-12-11 20:20 ` Ulrich Drepper
  0 siblings, 1 reply; 2+ messages in thread
From: H.J. Lu @ 1997-12-11 19:51 UTC (permalink / raw)
  To: egcs, GNU C Library; +Cc: Ulrich Drepper

I have to put

__register_frame_new; __register_frame_table_new; __deregister_frame_new;

in libc.map in glibc 2.1 after patching gcc 2.8.0 to compile glibc 2.1.
It is very tricky and the linker message doesn't help either. Can you
tell what

/usr/i586-unknown-linux-gnulibc1/bin/ld: /home/work/gnu/bin/glibc/db2/libdb.so: undefined version name __register_frame_table@@GLIBC_2.0

means?


-- 
H.J. Lu (hjl@gnu.org)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: gcc 2.8.0/egcs and glibc 2
  1997-12-11 19:51 gcc 2.8.0/egcs and glibc 2 H.J. Lu
@ 1997-12-11 20:20 ` Ulrich Drepper
  0 siblings, 0 replies; 2+ messages in thread
From: Ulrich Drepper @ 1997-12-11 20:20 UTC (permalink / raw)
  To: H.J. Lu; +Cc: egcs, GNU C Library

hjl@lucon.org (H.J. Lu) writes:

> It is very tricky and the linker message doesn't help either. Can you
> tell what
> 
> /usr/i586-unknown-linux-gnulibc1/bin/ld: /home/work/gnu/bin/glibc/db2/libdb.so: undefined version name __register_frame_table@@GLIBC_2.0
> 
> means?

Seems like an `ld' bug.  __register_frame_table@@GLIBC_2.0 is no
version name, GLIBC_2.0 is.  I've not yet tried gcc 2.8 so I cannot
tell more.

-- Uli
---------------.      drepper at gnu.org  ,-.   Rubensstrasse 5
Ulrich Drepper  \    ,-------------------'   \  76149 Karlsruhe/Germany
Cygnus Solutions `--' drepper at cygnus.com   `------------------------

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~1997-12-11 20:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-12-11 19:51 gcc 2.8.0/egcs and glibc 2 H.J. Lu
1997-12-11 20:20 ` Ulrich Drepper

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).