[Buildroot] Buildroot 2016.11-rc2 released

[Buildroot] Buildroot 2016.11-rc2 released

[Thomas Petazzoni]

Hi,

Buildroot 2016.11-rc2 is released - Go download it at:

http://buildroot.net/downloads/buildroot-2016.11-rc2.tar.gz

or

http://buildroot.net/downloads/buildroot-2016.11-rc2.tar.bz2

Or get it from Git:

git://git.buildroot.net/buildroot

Besides fixing a number of autobuilder failures, and updates to
defconfig to get more of them to build properly, a good number of
changes are related to fixing issues with the recent replacement of
'fakeroot' by 'pseudo'. Hopefully, it now works properly in all
situations.

Please give it a spin and report any problems to the mailing list or
bug tracker. Many thanks to the people contributing to this release:

git shortlog -sn 2016.11-rc1..
    23  Thomas Petazzoni
    10  Yann E. MORIN
     8  Ludovic Desroches
     8  Romain Naour
     6  Vicente Olivert Riera
     5  Baruch Siach
     4  J?r?me Pouiller
     3  Bernd Kuhls
     2  Arnout Vandecappelle
     2  Ga?l PORTAY
     2  Gustavo Zacarias
     2  Julien BOIBESSOT
     2  Peter Seiderer
     2  Rahul Bedarkar
     2  Waldemar Brodkorb
     2  Yegor Yefremov
     1  Cyril Bur
     1  Francois Perrad
     1  Frank Hunleth
     1  Gary Bisson
     1  Jan Viktorin
     1  J?rg Krause
     1  Maxime Hadjinlian
     1  Philippe Proulx
     1  Sam bobroff
     1  Samuel Martin
     1  Stefan Nickl
     1  Vincent Stehl?

For more details, see the CHANGES file:

http://git.buildroot.net/buildroot/plain/CHANGES?id=2016.11-rc2

Expect the final 2016.11 release by the end of the month.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Ricardo Martincoski]

Thomas De Schampheleire,
Max Filippov,

Do you see the issue described below? Maybe I am doing something wrong.
What bash version do you have in your RHEL5 servers?

All,

Ancient versions of bash don't support 'Associative arrays', leading to build
error using 2016.11-rc2 in a plain vanilla RHEL5.
Please notice EOL of RHEL5 is 31 Mar 2017 [1].
Currently the manual does not specify a minimum version of bash [2].

This is NOT my use case!
I was just testing some unrelated stuff in a VM and came across it.
I didn't tested the obvious workaround (installing a newer bash) but it should
work.

See below the logs for RHEL5 (error) and RHEL6 (ok).

[ricardo at centos5 buildroot-2016.11-rc2]$ grep release /etc/issue        
CentOS release 5.11 (Final)
[ricardo at centos5 buildroot-2016.11-rc2]$ bash --version | grep bash
GNU bash, version 3.2.25(1)-release (x86_64-redhat-linux-gnu)
[ricardo at centos5 buildroot-2016.11-rc2]$ make -s defconfig
support/scripts/br2-external: line 6: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
Makefile:188: /home/ricardo/buildroot-2016.11-rc2/output/.br-external.mk: No such file or directory
make[1]: Failed to remake makefile `/home/ricardo/buildroot-2016.11-rc2/output/.br-external.mk'.
support/scripts/br2-external: line 6: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
make[1]: *** [/home/ricardo/buildroot-2016.11-rc2/output/build/.br2-external.in] Error 2
make: *** [_all] Error 2

[ricardo at centos6 buildroot-2016.11-rc2]$ grep release /etc/issue        
CentOS release 6.8 (Final)
[ricardo at centos6 buildroot-2016.11-rc2]$ bash --version | grep bash
GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
[ricardo at centos6 buildroot-2016.11-rc2]$ make -s defconfig
#
# configuration written to /home/ricardo/buildroot-2016.11-rc2/.config
#

[1] https://wiki.centos.org/Download
[2] http://nightly.buildroot.org/manual.html#requirement-mandatory

Regards,
Ricardo

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Yann E. MORIN]

Ricardo, All,

On 2016-11-16 20:48 -0200, Ricardo Martincoski spake thusly:
> Do you see the issue described below? Maybe I am doing something wrong.
> What bash version do you have in your RHEL5 servers?
> 
> All,
> 
> Ancient versions of bash don't support 'Associative arrays', leading to build
> error using 2016.11-rc2 in a plain vanilla RHEL5.

Asociative arrays were introduced in bash-4.0, indeed.

Doing without associative arrays is not very easy. Rather, it would be
very difficult.

Unless the script is re-written in an other language...

> Please notice EOL of RHEL5 is 31 Mar 2017 [1].

Well, it's not even 6 months in the future. Time to upgrade, maybe? ;-)

> Currently the manual does not specify a minimum version of bash [2].

I think the best short-term solution is that we advertise that bash 4.0
is required, now.

Let's see what others think...

Regards,
Yann E. MORIN.


> This is NOT my use case!
> I was just testing some unrelated stuff in a VM and came across it.
> I didn't tested the obvious workaround (installing a newer bash) but it should
> work.
> 
> See below the logs for RHEL5 (error) and RHEL6 (ok).
> 
> [ricardo at centos5 buildroot-2016.11-rc2]$ grep release /etc/issue        
> CentOS release 5.11 (Final)
> [ricardo at centos5 buildroot-2016.11-rc2]$ bash --version | grep bash
> GNU bash, version 3.2.25(1)-release (x86_64-redhat-linux-gnu)
> [ricardo at centos5 buildroot-2016.11-rc2]$ make -s defconfig
> support/scripts/br2-external: line 6: declare: -A: invalid option
> declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
> Makefile:188: /home/ricardo/buildroot-2016.11-rc2/output/.br-external.mk: No such file or directory
> make[1]: Failed to remake makefile `/home/ricardo/buildroot-2016.11-rc2/output/.br-external.mk'.
> support/scripts/br2-external: line 6: declare: -A: invalid option
> declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
> make[1]: *** [/home/ricardo/buildroot-2016.11-rc2/output/build/.br2-external.in] Error 2
> make: *** [_all] Error 2
> 
> [ricardo at centos6 buildroot-2016.11-rc2]$ grep release /etc/issue        
> CentOS release 6.8 (Final)
> [ricardo at centos6 buildroot-2016.11-rc2]$ bash --version | grep bash
> GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
> [ricardo at centos6 buildroot-2016.11-rc2]$ make -s defconfig
> #
> # configuration written to /home/ricardo/buildroot-2016.11-rc2/.config
> #
> 
> [1] https://wiki.centos.org/Download
> [2] http://nightly.buildroot.org/manual.html#requirement-mandatory
> 
> Regards,
> Ricardo


-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Arnout Vandecappelle]

On 17-11-16 00:13, Yann E. MORIN wrote:
> Ricardo, All,
> 
> On 2016-11-16 20:48 -0200, Ricardo Martincoski spake thusly:
>> Do you see the issue described below? Maybe I am doing something wrong.
>> What bash version do you have in your RHEL5 servers?
>>
>> All,
>>
>> Ancient versions of bash don't support 'Associative arrays', leading to build
>> error using 2016.11-rc2 in a plain vanilla RHEL5.
> 
> Asociative arrays were introduced in bash-4.0, indeed.
> 
> Doing without associative arrays is not very easy. Rather, it would be
> very difficult.

 The associative arrays can be overcome relatively easily with eval; the indexed
array BR2_EXT_NAMES would be trickier to remove. This is possible because we
require the names to be only [A-Za-z0-9_] so they can be used as variable names.

 The idea is to do:

-    BR2_EXT_PATHS["${br2_name}"]="${br2_ext}"
+    eval BR2_EXT_PATH_${br2_name}='"${br2_ext}"'

and

-        printf ' %s' "${BR2_EXT_PATHS["${br2_name}"]}"
+        eval "printf ' %s' \"\${BR2_EXT_PATH_${br2_name}}\""

 It's horribly ugly, but it does work. Well, at least I think so :-)


 Regards,
 Arnout

> 
> Unless the script is re-written in an other language...
> 
>> Please notice EOL of RHEL5 is 31 Mar 2017 [1].
> 
> Well, it's not even 6 months in the future. Time to upgrade, maybe? ;-)
> 
>> Currently the manual does not specify a minimum version of bash [2].
> 
> I think the best short-term solution is that we advertise that bash 4.0
> is required, now.
> 
> Let's see what others think...
> 
> Regards,
> Yann E. MORIN.
> 
> 
>> This is NOT my use case!
>> I was just testing some unrelated stuff in a VM and came across it.
>> I didn't tested the obvious workaround (installing a newer bash) but it should
>> work.
>>
>> See below the logs for RHEL5 (error) and RHEL6 (ok).
>>
>> [ricardo at centos5 buildroot-2016.11-rc2]$ grep release /etc/issue        
>> CentOS release 5.11 (Final)
>> [ricardo at centos5 buildroot-2016.11-rc2]$ bash --version | grep bash
>> GNU bash, version 3.2.25(1)-release (x86_64-redhat-linux-gnu)
>> [ricardo at centos5 buildroot-2016.11-rc2]$ make -s defconfig
>> support/scripts/br2-external: line 6: declare: -A: invalid option
>> declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
>> Makefile:188: /home/ricardo/buildroot-2016.11-rc2/output/.br-external.mk: No such file or directory
>> make[1]: Failed to remake makefile `/home/ricardo/buildroot-2016.11-rc2/output/.br-external.mk'.
>> support/scripts/br2-external: line 6: declare: -A: invalid option
>> declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
>> make[1]: *** [/home/ricardo/buildroot-2016.11-rc2/output/build/.br2-external.in] Error 2
>> make: *** [_all] Error 2
>>
>> [ricardo at centos6 buildroot-2016.11-rc2]$ grep release /etc/issue        
>> CentOS release 6.8 (Final)
>> [ricardo at centos6 buildroot-2016.11-rc2]$ bash --version | grep bash
>> GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
>> [ricardo at centos6 buildroot-2016.11-rc2]$ make -s defconfig
>> #
>> # configuration written to /home/ricardo/buildroot-2016.11-rc2/.config
>> #
>>
>> [1] https://wiki.centos.org/Download
>> [2] http://nightly.buildroot.org/manual.html#requirement-mandatory
>>
>> Regards,
>> Ricardo
> 
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Yann E. MORIN]

Arnout, All,

On 2016-11-17 23:41 +0100, Arnout Vandecappelle spake thusly:
> On 17-11-16 00:13, Yann E. MORIN wrote:
> > Ricardo, All,
> > 
> > On 2016-11-16 20:48 -0200, Ricardo Martincoski spake thusly:
> >> Do you see the issue described below? Maybe I am doing something wrong.
> >> What bash version do you have in your RHEL5 servers?
> >>
> >> All,
> >>
> >> Ancient versions of bash don't support 'Associative arrays', leading to build
> >> error using 2016.11-rc2 in a plain vanilla RHEL5.
> > 
> > Asociative arrays were introduced in bash-4.0, indeed.
> > 
> > Doing without associative arrays is not very easy. Rather, it would be
> > very difficult.
> 
>  The associative arrays can be overcome relatively easily with eval;

Well, I am fully aware we could do it that way. That's not something I'd
have called "easy", though. It is technically easy, but the maintenance
burden is higher (as it is a trick).

> the indexed
> array BR2_EXT_NAMES would be trickier to remove.

Indexed arrays have been there since at least 3.0, released in 2004, so
even RHEL4 should have it...

> This is possible because we
> require the names to be only [A-Za-z0-9_] so they can be used as variable names.

Right. It's fortunate that kconfig does not allow variable names with a
dash or I'd have allowed that as well.

>  The idea is to do:
> 
> -    BR2_EXT_PATHS["${br2_name}"]="${br2_ext}"
> +    eval BR2_EXT_PATH_${br2_name}='"${br2_ext}"'
> 
> and
> 
> -        printf ' %s' "${BR2_EXT_PATHS["${br2_name}"]}"
> +        eval "printf ' %s' \"\${BR2_EXT_PATH_${br2_name}}\""
> 
>  It's horribly ugly, but it does work. Well, at least I think so :-)

Yes, something like this would work. But as you said, it is relatively
ugly. I had to maintain such a trick in the past and this is just a
nightmare...

For the records, RHEL5 standard support deadline in in March 2017, 4
months from now, but extended support is expected until 2021...

But oh well... We still need to know whether we still consider RHEL5 as
our oldest (unoffocially) supported platform, or if we just bite the
bullet and require bash-4.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Arnout Vandecappelle]

On 19-11-16 09:39, Yann E. MORIN wrote:
> But oh well... We still need to know whether we still consider RHEL5 as
> our oldest (unoffocially) supported platform, or if we just bite the
> bullet and require bash-4.

 ThomasDS asked if it would be possible to support RHEL5 if you don't use
BR2_EXTERNAL. Do you think that's feasible?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Yann E. MORIN]

Arnout, All,

On 2016-11-19 10:05 +0100, Arnout Vandecappelle spake thusly:
> On 19-11-16 09:39, Yann E. MORIN wrote:
> > But oh well... We still need to know whether we still consider RHEL5 as
> > our oldest (unoffocially) supported platform, or if we just bite the
> > bullet and require bash-4.
> 
>  ThomasDS asked if it would be possible to support RHEL5 if you don't use
> BR2_EXTERNAL. Do you think that's feasible?

No.

Well, all is possible. But the cost would be too high, IMHO...

I have a patch locally that fakes asociative arrays usingeval as you
suggested. I'm testing it right now (it still works fien with bash-4,
at least! :-)). If it works with bash-3.1, I'll send it.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Max Filippov]

On Wed, Nov 16, 2016 at 2:48 PM, Ricardo Martincoski
<ricardo.martincoski@gmail.com> wrote:
> Do you see the issue described below? Maybe I am doing something wrong.
> What bash version do you have in your RHEL5 servers?

Yes, I have this issue. It was introduced by the commit 20cd49738781b ("core:
add support for multiple br2-external trees").

-- 
Thanks.
-- Max

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Arnout Vandecappelle]

On 17-11-16 00:14, Max Filippov wrote:
> On Wed, Nov 16, 2016 at 2:48 PM, Ricardo Martincoski
> <ricardo.martincoski@gmail.com> wrote:
>> Do you see the issue described below? Maybe I am doing something wrong.
>> What bash version do you have in your RHEL5 servers?
> 
> Yes, I have this issue. It was introduced by the commit 20cd49738781b ("core:
> add support for multiple br2-external trees").

 Would any of you RHEL5 users be able to contribute an autobuilder instance so
this kind of issue can be detected on time?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Ricardo Martincoski]

Arnout,

On Thu, Nov 17, 2016 at 08:43 PM, Arnout Vandecappelle wrote:

> On 17-11-16 00:14, Max Filippov wrote:
>> On Wed, Nov 16, 2016 at 2:48 PM, Ricardo Martincoski
>> <ricardo.martincoski@gmail.com> wrote:
>>> Do you see the issue described below? Maybe I am doing something wrong.
>>> What bash version do you have in your RHEL5 servers?
>> 
>> Yes, I have this issue. It was introduced by the commit 20cd49738781b ("core:
>> add support for multiple br2-external trees").
> 
>  Would any of you RHEL5 users be able to contribute an autobuilder instance so
> this kind of issue can be detected on time?

I sent the e-mail as a heads up to the real users of RHEL5.
From past e-mails, I know Thomas DS and Max are (or were) users.

For me it's only a VM I sporadically use for tests only.
I installed bash v4 and resumed my testings.

Just trying to help. Sorry any confusion.

Regards,
Ricardo

[Buildroot] 2016.11-rc2 with really old versions of bash (RHEL5)

[Thomas De Schampheleire]

Hi all,

On Fri, Nov 18, 2016 at 5:50 AM, Ricardo Martincoski
<ricardo.martincoski@gmail.com> wrote:
> Arnout,
>
> On Thu, Nov 17, 2016 at 08:43 PM, Arnout Vandecappelle wrote:
>
>> On 17-11-16 00:14, Max Filippov wrote:
>>> On Wed, Nov 16, 2016 at 2:48 PM, Ricardo Martincoski
>>> <ricardo.martincoski@gmail.com> wrote:
>>>> Do you see the issue described below? Maybe I am doing something wrong.
>>>> What bash version do you have in your RHEL5 servers?
>>>
>>> Yes, I have this issue. It was introduced by the commit 20cd49738781b ("core:
>>> add support for multiple br2-external trees").
>>
>>  Would any of you RHEL5 users be able to contribute an autobuilder instance so
>> this kind of issue can be detected on time?
>
> I sent the e-mail as a heads up to the real users of RHEL5.
> From past e-mails, I know Thomas DS and Max are (or were) users.
>

True, I still need to support some RHEL5 machines, although the
majority is at RHEL6 and RHEL7 (or CentOS equivalents).
We are not using BR2_EXTERNAL though, so if I could get around it by
making sure the script is not actually called, I would be fine.

So strictly speaking for my own needs, I wouldn't really mind requiring bash 4.
(but please don't start using bash 4 features in other,
non-br2-external scripts just yet :-) )

Best regards,
Thomas