public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: libc-hacker@sources.redhat.com
Subject: glibc 2.2 cvs on AXP: undefined symbol: atexit
Date: Fri, 12 Apr 2002 04:43:00 -0000	[thread overview]
Message-ID: <20020412134306.A1373@suse.de> (raw)


Hi,

If I try to compile the current glibc 2.2 branch on Alpha, I always get
this error:

/usr/src/packages/BUILD/glibc-2.2/cc/sunrpc/rpcgen: relocation error: /usr/src/packages/BUILD/glibc-2.2/cc/libc.so.6.1: undefined symbol: atexit
make[2]: *** [/usr/src/packages/BUILD/glibc-2.2/cc/sunrpc/xbootparam_prot.stmp] 
Error 127


It seems that the following patch is the reason for this. Is the fix wrong,
or is there another bug on Alpha which is triggerd with this change?

  Thorsten


2002-04-02  Ulrich Drepper  <drepper@redhat.com>

        * elf/do-lookup.h (do_lookup): 2 is the first user-defined version
        number [PR libc/3111].

--- elf/do-lookup.h	Mon Aug 27 00:24:08 2001
+++ elf/do-lookup.h	Wed Apr  3 16:34:15 2002
@@ -128,7 +128,7 @@
 	  if (verstab != NULL)
 	    {
 	      ElfW(Half) ndx = verstab[symidx] & 0x7fff;
-	      if (ndx > 2) /* map->l_versions[ndx].hash != 0) */
+	      if (ndx >= 2) /* map->l_versions[ndx].hash != 0) */
 		{
 		  /* Don't accept hidden symbols.  */
 		  if ((verstab[symidx] & 0x8000) == 0 && num_versions++ == 0)


-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Deutschherrenstr. 15-19       D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

             reply	other threads:[~2002-04-12 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  4:43 Thorsten Kukuk [this message]
2002-04-12  9:03 ` H . J . Lu
2002-04-12 10:30   ` Thorsten Kukuk
2002-04-12 10:34 ` Ulrich Drepper

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=20020412134306.A1373@suse.de \
    --to=kukuk@suse.de \
    --cc=libc-hacker@sources.redhat.com \
    /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).