public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaro.koskinen at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63691] New: GCC 4.9.x fails to build GLIBC 2.20 on HPPA
Date: Thu, 30 Oct 2014 21:19:00 -0000 [thread overview]
Message-ID: <bug-63691-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63691
Bug ID: 63691
Summary: GCC 4.9.x fails to build GLIBC 2.20 on HPPA
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: aaro.koskinen at iki dot fi
GCC 4.8.3 builds GLIBC 2.20 (w/Gentoo patches) fine, but with GCC 4.9 it fails:
hppa-linux-gnu-gcc -nostdlib -nostartfiles -r -o
/home/aaro/los/work/parisc/glibc-2.20-build/default/elf/librtld.map.o '-Wl,-('
/home/aaro/los/work/parisc/glibc-2.20-build/default/elf/dl-allobjs.os
/home/aaro/los/work/parisc/glibc-2.20-build/default/libc_pic.a -lgcc '-Wl,-)'
-Wl,-Map,/home/aaro/los/work/parisc/glibc-2.20-build/default/elf/librtld.mapT
/home/aaro/los/work/parisc/glibc-2.20-build/default/libc_pic.a(dl-addr.os): In
function `_dl_addr_inside_object':
/home/aaro/los/work/shared/glibc-2.20/elf/dl-addr.c:152: multiple definition of
`_dl_addr_inside_object'
/home/aaro/los/work/parisc/glibc-2.20-build/default/elf/dl-allobjs.os:(.text+0x8b8):
first defined here
/home/aaro/los/work/parisc/glibc-2.20-build/default/libc_pic.a(init-first.os):(.data+0x0):
multiple definition of `__libc_multiple_libcs'
/home/aaro/los/work/parisc/glibc-2.20-build/default/elf/dl-allobjs.os:(.bss+0x7c):
first defined here
/home/aaro/los/work/parisc/glibc-2.20-build/default/libc_pic.a(_itoa.os): In
function `_itoa':
/home/aaro/los/work/shared/glibc-2.20/stdio-common/_itoa.c:199: multiple
definition of `_itoa'
/home/aaro/los/work/parisc/glibc-2.20-build/default/elf/dl-allobjs.os:(.text+0x5b8):
first defined here
collect2: error: ld returned 1 exit status
next reply other threads:[~2014-10-30 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 21:19 aaro.koskinen at iki dot fi [this message]
2014-10-30 21:27 ` [Bug target/63691] " aaro.koskinen at iki dot fi
2014-10-31 0:29 ` dave.anglin at bell dot net
2014-10-31 0:49 ` pinskia at gcc dot gnu.org
2014-10-31 1:18 ` pinskia at gcc dot gnu.org
2014-10-31 18:43 ` aaro.koskinen at iki dot fi
2014-10-31 19:43 ` dave.anglin at bell dot net
2014-10-31 21:52 ` aaro.koskinen at iki dot fi
2014-11-01 8:17 ` schwab@linux-m68k.org
2014-11-01 11:32 ` aaro.koskinen at iki dot fi
2014-11-01 14:34 ` danglin at gcc dot gnu.org
2014-11-04 19:36 ` aaro.koskinen at iki dot fi
2021-11-28 14:43 ` danglin 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-63691-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).