public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build warning
Date: Mon, 10 Oct 2022 15:11:05 +1100	[thread overview]
Message-ID: <20221010151105.0504dfa2@canb.auug.org.au> (raw)
In-Reply-To: <20221010144134.1a806e7d@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

Hi all,

On Mon, 10 Oct 2022 14:41:34 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> My linux-next builds have started producing these warnings:
> 
> ld: warning: .tmp_vmlinux.kallsyms1 has a LOAD segment with RWX permissions
> ld: warning: .tmp_vmlinux.kallsyms2 has a LOAD segment with RWX permissions
> ld: warning: vmlinux has a LOAD segment with RWX permissions
> 
> I assume that these turned up now because I upgraded my binutils to 2.39
> but I have no idea what the root cause is.

Probably a false alarm due to me upgrading binutils while the builds
were in progress :-)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-10-10  4:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  3:41 linux-next: build warning Stephen Rothwell
2022-10-10  4:11 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-24  6:38 Stephen Rothwell
2008-11-24  7:53 ` NeilBrown
2008-11-24  9:14   ` Stephen Rothwell
2008-10-16  6:04 Stephen Rothwell
2008-10-16 16:04 ` Greg KH
2008-09-18 21:17 Stephen Rothwell
2008-09-27  1:17 ` Steven Rostedt
2008-08-29  8:14 Stephen Rothwell
2008-08-29 12:09 ` Jason Wessel

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=20221010151105.0504dfa2@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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