public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tpsa.s.a at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/56467] New: gcc fails to link binaries with unknown reference complaint Date: Tue, 26 Feb 2013 18:13:00 -0000 [thread overview] Message-ID: <bug-56467-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56467 Bug #: 56467 Summary: gcc fails to link binaries with unknown reference complaint Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: tpsa.s.a@gmail.com Created attachment 29545 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29545 archive of 3 typescripts for gcc 4.4,4.6,4.7 and *.i for gccs and file with uname -a and list of packages gcc 4.7.2 and 4.6.3 fails to link binaries with dynamic library librt.so.1 (in /usr/lib/i386-linux-gnu/) with unknown reference complaint. Earlier version 4.4.7 links successfully the same code.
next reply other threads:[~2013-02-26 18:13 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-26 18:13 tpsa.s.a at gmail dot com [this message] 2013-02-26 18:21 ` [Bug c/56467] " redi at gcc dot gnu.org 2014-03-26 7:57 ` mpolacek 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-56467-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: linkBe 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).