From: Alan Modra <amodra@gmail.com>
To: Brian Groose <brian@groose.com>
Cc: binutils@sourceware.org
Subject: Re: Linux ppc64 - compatibility-ldbl.o can't find std::num_put
Date: Sat, 13 Apr 2019 02:57:00 -0000 [thread overview]
Message-ID: <20190413025656.GL14424@bubble.grove.modra.org> (raw)
In-Reply-To: <CAKMEP22bqYXsbDrViAmFdWJ4AQ26sSJbGOTC23-hXSpDA_Qjag@mail.gmail.com>
On Wed, Apr 10, 2019 at 12:52:59PM -0400, Brian Groose wrote:
> It looks like I'm hitting the same issue that was reported in this
> invalid gcc bug, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43968,
> which was closed because it is a binutils bug?
No, that old ar bug won't be the trouble here.
> I'm getting the exact same errors but running Linux on ppc64 instead
> of alpha. I have built binutils 2.25.1 and 2.32 from source, and both
> have hit the same linker errors as in that gcc bug. The same code
> with the same binutils and gcc versions links without error on Linux
> x86 and x64 (and 32-bit Solaris targets).
>
> I am NOT linking with -static, though I am using -static-libgcc and
> -static-libstdc++. I am unable to reproduce this with a small test
> case program such as the one found in the gcc bug.
>
> Can anyone give me any suggestions of things to try here or what might be wrong?
I don't know what to suggest with the few details you've supplied.
I think you'll find that the missing compatibility-ldbl.o symbols are
defined in locale-inst.o, also in libstdc++.a. So it's a mystery why
they don't satisfy the references. Have you tried newer versions of
gcc?
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2019-04-13 2:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 16:53 Brian Groose
2019-04-13 2:57 ` Alan Modra [this message]
2019-04-13 17:32 ` Brian Groose
2019-04-14 23:16 ` Alan Modra
2019-04-15 15:16 ` Brian Groose
[not found] ` <20190416102257.GR14424@bubble.grove.modra.org>
[not found] ` <CAKMEP22JpJ2kZudtYCX-zLkGwDcsNcDcLPQZSnSAW4LBzObc3Q@mail.gmail.com>
[not found] ` <20190417003822.GZ14424@bubble.grove.modra.org>
[not found] ` <CAKMEP22iLBSHNBYjhSQM7MubcjQQ0vaJo4cru0sP+3Y6y-ZOdA@mail.gmail.com>
[not found] ` <CAKMEP22ci3Wu-OVhkMMb91fhxD23WX4rEEv9YohDHg6PxozurQ@mail.gmail.com>
2019-04-23 10:49 ` Alan Modra
2019-04-23 20:33 ` Brian Groose
2019-04-24 13:54 ` Alan Modra
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=20190413025656.GL14424@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brian@groose.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).