From: Joel Stanley <joel@jms.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Alan Modra <amodra@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings from Linus' tree
Date: Wed, 14 Nov 2018 15:24:04 +1030 [thread overview]
Message-ID: <CACPK8XeDHt46rUJWQ1n=4fRWioogs9K0Z8dkxUa=E2ShfQ1Vdg@mail.gmail.com> (raw)
In-Reply-To: <20180612081413.323d85b8@canb.auug.org.au>
Hello Alan,
On Tue, 12 Jun 2018 at 07:44, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Building Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
> produced these warning:
>
> ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'.
> ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'.
> ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'.
>
> This may just be because I have started building using the native Debian
> gcc for the powerpc builds ...
Do you know why we started creating these?
If it's intentional, should we be putting including them in the same
way as .hash sections?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/kernel/vmlinux.lds.S#n282
.hash : AT(ADDR(.hash) - LOAD_OFFSET) { *(.hash) }
Cheers,
Joel
next prev parent reply other threads:[~2018-11-14 4:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 22:14 linux-next: build warnings from Linus' tree Stephen Rothwell
2018-11-14 4:54 ` Joel Stanley [this message]
2018-11-14 10:20 ` Michael Ellerman
2018-11-18 11:22 ` Alan Modra
2018-12-03 23:24 ` Joel Stanley
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 21:59 Stephen Rothwell
2018-08-19 22:13 Stephen Rothwell
2018-08-19 22:16 ` Stephen Rothwell
2018-08-19 22:40 ` Stephen Rothwell
2018-08-19 23:21 ` Linus Torvalds
2018-08-20 1:33 ` Adam Borowski
2018-08-20 2:53 ` Theodore Y. Ts'o
2018-08-20 0:02 ` Theodore Y. Ts'o
2018-08-20 17:47 ` Miguel Ojeda
2010-10-28 0:27 Stephen Rothwell
2010-10-28 3:04 ` Mark Brown
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='CACPK8XeDHt46rUJWQ1n=4fRWioogs9K0Z8dkxUa=E2ShfQ1Vdg@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=amodra@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).