From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the powerpc-fixes tree
Date: Tue, 22 Apr 2025 11:20:38 +0530 [thread overview]
Message-ID: <157256be-d77d-427e-8feb-77d1373b0c00@linux.ibm.com> (raw)
In-Reply-To: <20250422114720.480cea29@canb.auug.org.au>
On 4/22/25 7:17 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the powerpc-fixes tree, today's linux-next build
> (powerpc_ppc64_defconfig) produced these warnings:
>
> arch/powerpc/boot/wrapper: 237: [: 0: unexpected operator
> ld: warning: arch/powerpc/boot/zImage.epapr has a LOAD segment with RWX permissions
> arch/powerpc/boot/wrapper: 237: [: 0: unexpected operator
> ld: warning: arch/powerpc/boot/zImage.pseries has a LOAD segment with RWX permissions
> arch/powerpc/boot/wrapper: 237: [: 0: unexpected operator
> ld: warning: arch/powerpc/boot/zImage.pmac has a LOAD segment with RWX permissions
> arch/powerpc/boot/wrapper: 237: [: 0: unexpected operator
> ld: warning: arch/powerpc/boot/dtbImage.ps3 has a LOAD segment with RWX permissions
>
I cant recreate this in both my x86_64 cross build and ppc64 build with dash.
I tried both ppc64_defconfig and pseries_le_defconfig compilation.
x86_64 dash version : dash-0.5.12-3.fc40.x86_64
powerpc dash version : dash-0.5.12-4.fc41.ppc64le
Can you share the dash version
Maddy
> Introduced by commit
>
> b2accfe7ca5b ("powerpc/boot: Check for ld-option support")
>
> POSIX shell (in particular dash) does not recognise "&>" - you need to
> use ">/dev/null 2>&1". (My /bin/sh is /bin/dash)
>
next prev parent reply other threads:[~2025-04-22 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 1:47 linux-next: build warnings after merge of the powerpc-fixes tree Stephen Rothwell
2025-04-22 5:50 ` Madhavan Srinivasan [this message]
2025-04-22 6:15 ` Stephen Rothwell
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=157256be-d77d-427e-8feb-77d1373b0c00@linux.ibm.com \
--to=maddy@linux.ibm.com \
--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 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.