From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
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 16:15:01 +1000 [thread overview]
Message-ID: <20250422161501.306c2712@canb.auug.org.au> (raw)
In-Reply-To: <157256be-d77d-427e-8feb-77d1373b0c00@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
Hi Madhavan,
On Tue, 22 Apr 2025 11:20:38 +0530 Madhavan Srinivasan <maddy@linux.ibm.com> wrote:
>
> 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
I am running Debian Testing on ppc64el and the dash version is
0.5.12-12.
Try this:
$ make -p 2>/dev/null | grep -w SHELL
SHELL = /bin/sh
$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Feb 5 00:14 /bin/sh -> dash
$ dash -c '[ $(ld -v --no-warn-rwx-segments &>/dev/null; echo $?) -eq 0 ]'
dash: 1: [: 0: unexpected operator
$ dash -c 'x=$(ld -v --no-warn-rwx-segments &>/dev/null; echo $?); echo "$x"'
0
GNU ld (GNU Binutils for Debian) 2.44
i.e. the $( ... ) returns 2 lines of output because the "ld ..." part is
backgrounded by the '&'.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-04-22 6:15 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
2025-04-22 6:15 ` Stephen Rothwell [this message]
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=20250422161501.306c2712@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.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