public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/64812] [4.9 regression] x86 LibreOffice Build failure: undefined reference to acquire Date: Fri, 27 Feb 2015 08:39:00 -0000 [thread overview] Message-ID: <bug-64812-4-sJkFuyDWeC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64812-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64812 --- Comment #8 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Also happens with gcc-5 when linking two different LibreOffice libraries. (libscfiltlo.so and libooxlo.so) The undefined symbol is: x4 ~ # c++filt _ZThn40_N3utl28OSeekableOutputStreamWrapper7acquireEv non-virtual thunk to utl::OSeekableOutputStreamWrapper::acquire() But the symbol is defined in workdir/CxxObject/unotools/source/streaming/streamwrap.o and adding this object file to the link object file list fixes the problem. So it looks like a LibreOffice issue in this case.
next prev parent reply other threads:[~2015-02-27 7:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-27 2:48 [Bug regression/64812] New: " lukebenes at hotmail dot com 2015-01-27 6:48 ` [Bug regression/64812] " trippels at gcc dot gnu.org 2015-01-27 6:56 ` trippels at gcc dot gnu.org 2015-01-27 11:11 ` rguenth at gcc dot gnu.org 2015-02-04 9:33 ` timo.teras at iki dot fi 2015-02-13 18:04 ` basile at opensource dot dyc.edu 2015-02-16 14:10 ` mstahl at redhat dot com 2015-02-16 14:14 ` mstahl at redhat dot com 2015-02-27 8:39 ` trippels at gcc dot gnu.org [this message] 2015-02-27 14:23 ` [Bug ipa/64812] " mstahl at redhat dot com 2015-02-27 14:48 ` trippels at gcc dot gnu.org 2015-06-26 20:18 ` jakub at gcc dot gnu.org 2015-06-26 20:39 ` jakub 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-64812-4-sJkFuyDWeC@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).