public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "deadjdona at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16261] New: /root/glibc18-build/elf/tst-unique3lib.os:(.data.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0): undefined reference to `__gxx_personality_v0'
Date: Wed, 27 Nov 2013 10:42:00 -0000	[thread overview]
Message-ID: <bug-16261-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16261

            Bug ID: 16261
           Summary: /root/glibc18-build/elf/tst-unique3lib.os:(.data.DW.re
                    f.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x
                    0): undefined reference to `__gxx_personality_v0'
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: deadjdona at gmail dot com
                CC: drepper.fsp at gmail dot com

good day.

i'm trying to compile glibc 2.18 under centos 

Linux virtualhost 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux

make check fail to finish with following error:

gcc   -shared -static-libgcc  -Wl,-dynamic-linker=/lib64/ld-linux-x86-64.so.2
-Wl,-z,defs -B/root/glibc18-build/csu/  -Wl,-z,combreloc -Wl,-z,relro
-Wl,--hash-style=both  -L/root/glibc18-build -L/root/glibc18-build/math
-L/root/glibc18-build/elf -L/root/glibc18-build/dlfcn -L/root/glibc18-build/nss
-L/root/glibc18-build/nis -L/root/glibc18-build/rt -L/root/glibc18-build/resolv
-L/root/glibc18-build/crypt -L/root/glibc18-build/nptl
-Wl,-rpath-link=/root/glibc18-build:/root/glibc18-build/math:/root/glibc18-build/elf:/root/glibc18-build/dlfcn:/root/glibc18-build/nss:/root/glibc18-build/nis:/root/glibc18-build/rt:/root/glibc18-build/resolv:/root/glibc18-build/crypt:/root/glibc18-build/nptl
-o /root/glibc18-build/elf/tst-unique3lib.so -T /root/glibc18-build/shlib.lds
/root/glibc18-build/csu/abi-note.o /root/glibc18-build/elf/tst-unique3lib.os 
-Wl,--start-group /root/glibc18-build/libc.so
/root/glibc18-build/libc_nonshared.a -Wl,--as-needed
/root/glibc18-build/elf/ld.so -Wl,--no-as-needed -Wl,--end-group
/root/glibc18-build/elf/tst-unique3lib.os:(.data.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0):
undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status
make[2]: *** [/root/glibc18-build/elf/tst-unique3lib.so] Error 1
rm /root/glibc18-build/elf/ld.dynsym /root/glibc18-build/libc.dynsym
make[2]: Leaving directory `/root/glibc-2.18/elf'
make[1]: *** [elf/tests] Error 2
make[1]: Leaving directory `/root/glibc-2.18'
make: *** [check] Error 2

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-11-27 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 10:42 deadjdona at gmail dot com [this message]
2014-02-07  3:04 ` [Bug build/16261] " jsm28 at gcc dot gnu.org
2014-06-13 11:51 ` fweimer at redhat dot com
2014-08-07 20:58 ` cmetcalf at tilera dot com
2015-01-24 12:22 ` chengm349 at hotmail dot com
2015-08-24  9:48 ` jsm28 at gcc dot gnu.org

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=bug-16261-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).