public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2672] New: going libc_pic.a to libc_pic.os discard gets into the way
Date: Wed, 17 May 2006 18:00:00 -0000 [thread overview]
Message-ID: <20060517180018.2672.malitzke@metronets.com> (raw)
It looks to me that gcc is more incidental here and that really binutils is
doing the work
gcc -nostdlib -nostartfiles -r -o /usr/src/glibc-23/build/libc_pic.os
-Wl,-d -Wl,--whole-archive /usr/src/glibc-23/build/libc_pic.a
.LANCHOR0' referenced in section `.text' of
/usr/src/glibc-23/build/libc_pic.a(strtoul_l.os): defined in discarded section
`.gnu.linkonce.r.__strtol_ul_max_tab' of
collect2: ld returned 1 exit status
make[1]: *** [/usr/src/glibc-23/build/libc_pic.os] Error 1
make[1]: Leaving directory `/usr/src/glibc-23/glibc-2.3.7'
make: *** [all] Error 2
--
Summary: going libc_pic.a to libc_pic.os discard gets into the
way
Product: glibc
Version: 2.4
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: malitzke at metronets dot com
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: powerpc
GCC host triplet: powerpc
GCC target triplet: powerpc
http://sourceware.org/bugzilla/show_bug.cgi?id=2672
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-05-17 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 18:00 malitzke at metronets dot com [this message]
2006-05-17 18:04 ` [Bug libc/2672] " malitzke at metronets dot com
2006-05-17 18:42 ` decimal at us dot ibm dot com
2006-08-04 2:39 ` pinskia at gcc dot gnu dot org
2006-08-04 2:39 ` pinskia at gcc dot gnu dot org
2006-08-04 15:22 ` pinskia at gcc dot gnu dot org
2006-08-04 15:22 ` pinskia at gcc dot gnu dot org
2006-08-10 6:17 ` pinskia at gcc dot gnu dot org
2006-08-10 6:19 ` pinskia at gcc dot gnu dot org
2006-08-24 6:58 ` drepper at redhat dot com
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=20060517180018.2672.malitzke@metronets.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).