From: Alan Modra <amodra@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/3] minor build fixes
Date: Thu, 24 Nov 2016 09:33:20 +1030 [thread overview]
Message-ID: <20161123230320.GQ11815@bubble.grove.modra.org> (raw)
In-Reply-To: <20161123130209.1667-1-npiggin@gmail.com>
On Thu, Nov 24, 2016 at 12:02:06AM +1100, Nicholas Piggin wrote:
> I was building BookE and big endian with a little endian cross
> compiler and it stopped working. My BookS BE tests must have been
> building using the ELFv2 ABI. After this, the build sometimes still
> strangely fails with dot symbols in syscall table unable to be found,
> but that's looking like it may be a linker bug (Alan is going to take
> a look).
Yes it is a bug. In compatibility code that was supposed to handle
mixing old object files that use dot-symbols on function entry with
newer object files that don't. Here, "old" means mid 2004 or
earlier.
As you can imagine, I'm not hugely concerned about the ld bug..
Since every binutils back to at least 2.17 has the bug, what changed
in the kernel to expose it? Are you building without -mcall-aixdesc?
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2016-11-23 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 13:02 [PATCH 0/3] minor build fixes Nicholas Piggin
2016-11-23 13:02 ` [PATCH 1/3] powerpc/64e: convert cmpi to cmpwi in head_64.S Nicholas Piggin
2016-11-29 12:58 ` [1/3] " Michael Ellerman
2016-11-23 13:02 ` [PATCH 2/3] powerpc: allow compilation on cross-endian toolchain Nicholas Piggin
2016-11-24 9:04 ` Nicholas Piggin
2016-11-26 3:00 ` Nicholas Piggin
2016-11-26 7:30 ` Michael Ellerman
2016-11-27 2:46 ` Nicholas Piggin
2017-02-02 8:08 ` Naveen N. Rao
2017-03-08 7:25 ` [2/3] " Michael Ellerman
2016-11-23 13:02 ` [PATCH 3/3] powerpc/64e: don't branch to dot symbols Nicholas Piggin
2016-11-29 12:58 ` [3/3] " Michael Ellerman
2016-11-23 23:03 ` Alan Modra [this message]
2016-11-24 1:04 ` [PATCH 0/3] minor build fixes Nicholas Piggin
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=20161123230320.GQ11815@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.