From: Russell King <rmk@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: linux-next: build failure after merge of the arm-current tree
Date: Wed, 18 Apr 2018 18:54:43 +0100 [thread overview]
Message-ID: <20180418175442.GA7234@flint.armlinux.org.uk> (raw)
In-Reply-To: <20180418133155.0931baf7@canb.auug.org.au>
On Wed, Apr 18, 2018 at 01:31:55PM +1000, Stephen Rothwell wrote:
> Hi Russell,
>
> After merging the arm-current tree, today's linux-next build
> (lots of configs) failed like this:
>
> /bin/sh: 1: arithmetic expression: expecting primary: " "
> (lots of these)
>
> Caused by commit
>
> fe680ca02c1e ("ARM: replace unnecessary perl with sed and the shell $(( )) operator")
>
> (pointed out by Michael Ellerman)
>
> Our /bin/sh is dash not bash ...
I tested this on 32-bit ARM with dash:
foo# dash
# echo $(($(nm /boot/vmlinux-4.16.0+ | sed -n -e 's/^\([^ ]*\) B __bss_start$/-0x\1/p' -e 's/^\([^ ]*\) B __bss_stop$/+0x\1/p') ))
6409680
#
Any clues what '/bin/sh: 1: arithmetic expression: expecting primary: " "'
actually means in reality?
I don't see why you should end up with lots of them either, unless maybe
the sed expression isn't working for you.
The sed expression should end up producing output such as:
-0xc09138c4
+0xc0f30694
and that's it, two values, one preceded by a + and the other by a -.
--
Russell King
ARM architecture Linux Kernel maintainer
next prev parent reply other threads:[~2018-04-18 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 3:31 linux-next: build failure after merge of the arm-current tree Stephen Rothwell
2018-04-18 17:54 ` Russell King [this message]
2018-04-18 18:17 ` Russell King
2018-04-18 23:51 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-04-10 0:29 Stephen Rothwell
2015-04-10 7:28 ` Russell King - ARM Linux
2015-04-10 8:08 ` 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=20180418175442.GA7234@flint.armlinux.org.uk \
--to=rmk@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.