From: Ulrich Drepper <drepper@gnu.org>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com, libc-linux@gnu.org (GNU C Library)
Subject: Re: gcc 2.8.0/egcs and glibc 2
Date: Thu, 11 Dec 1997 20:20:00 -0000 [thread overview]
Message-ID: <x74t4f19ew.fsf@myware.rz.uni-karlsruhe.de> (raw)
In-Reply-To: <m0xgM8d-0004ecC@ocean.lucon.org>
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 `------------------------
prev parent reply other threads:[~1997-12-11 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-11 19:51 H.J. Lu
1997-12-11 20:20 ` Ulrich Drepper [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=x74t4f19ew.fsf@myware.rz.uni-karlsruhe.de \
--to=drepper@gnu.org \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=libc-linux@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).