From: Dirk Behme <dirk.behme@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman reports error of script/binutils-version.sh
Date: Tue, 23 Dec 2014 15:33:05 +0100 [thread overview]
Message-ID: <54997D21.3020303@gmail.com> (raw)
In-Reply-To: <CAPnjgZ3OsGae-xeT23MkMzdf5WXfr=MYPh8DqFBruTVLHujx+g@mail.gmail.com>
On 23.11.2014 23:20, Simon Glass wrote:
> Hi,
>
> On 21 November 2014 at 16:36, York Sun <yorksun@freescale.com> wrote:
>> Simon,
>>
>> Shall we consider host error to be an error reported by buildman? I happen to
>> try a newer version of toolchain from Linaro. Buildman reports this error
>>
>>
>> +../scripts/binutils-version.sh: line 20: printf: 09: invalid octal number
>>
>> The root cause is this version of AS reports version string differently
>>
>> GNU assembler (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09)
>> 2.24.0.20140829 Linaro 2014.09
>>
>> It has "Linaro 2014.09" at the back, so script/binutils-version.sh cannot parse
>> it correctly (the error is not handling zero-leading numbers, but not in the
>> scope of this discussion).
>>
>> Another angle of this question is, why do we need this script? It doesn't sound
>> stable to me to parse the version string this way.
>
> That's another one in Masahiro's domain I think.
Are there any news/answers/fixes for this?
I'm getting above
+../scripts/binutils-version.sh: line 20: printf: 09: invalid octal number
too, with the Linaro 2014.09 tool chain.
Thanks,
Dirk
next prev parent reply other threads:[~2014-12-23 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 23:36 [U-Boot] buildman reports error of script/binutils-version.sh York Sun
2014-11-23 22:20 ` Simon Glass
2014-12-23 14:33 ` Dirk Behme [this message]
2014-12-25 2:15 ` Masahiro Yamada
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=54997D21.3020303@gmail.com \
--to=dirk.behme@gmail.com \
--cc=u-boot@lists.denx.de \
/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.