* [U-Boot] [ANN] U-Boot v2019.10-rc2 released
@ 2019-08-13 22:26 Tom Rini
2019-08-21 8:23 ` Peter Robinson
0 siblings, 1 reply; 4+ messages in thread
From: Tom Rini @ 2019-08-13 22:26 UTC (permalink / raw)
To: u-boot
Hey all,
It's the day after the scheduled release day, and here is v2019.10-rc2.
It took me a while to confirm that the riscv PR was causing the issue I
saw, and I got extra paranoid about testing all of the other PRs to be
sure it really was that and not some other race condition. At this
point, it's time to aim to stabilize everything. That said, I think
there's at least one or two trees that haven't sent their big PR yet and
I'd like to see that come in as soon as possible.
In terms of a changelog,
git log --merges v2019.10-rc1..v2019.10-rc2
continues to look pretty good but the content there varies based on what
was given to me in the PR. So please, the more details in the request
the better!
I'm still planning on doing -rc3 on the 26th of August with -rc4 on
September 9th and -rc5 on September 23rd with the release scheduled on
October 7th. Thanks all!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190813/89dc6716/attachment.sig>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] [ANN] U-Boot v2019.10-rc2 released
2019-08-13 22:26 [U-Boot] [ANN] U-Boot v2019.10-rc2 released Tom Rini
@ 2019-08-21 8:23 ` Peter Robinson
2019-08-24 1:50 ` David Abdurachmanov
0 siblings, 1 reply; 4+ messages in thread
From: Peter Robinson @ 2019-08-21 8:23 UTC (permalink / raw)
To: u-boot
Hi Simon,
> It's the day after the scheduled release day, and here is v2019.10-rc2.
> It took me a while to confirm that the riscv PR was causing the issue I
> saw, and I got extra paranoid about testing all of the other PRs to be
> sure it really was that and not some other race condition. At this
> point, it's time to aim to stabilize everything. That said, I think
> there's at least one or two trees that haven't sent their big PR yet and
> I'd like to see that come in as soon as possible.
>
> In terms of a changelog,
> git log --merges v2019.10-rc1..v2019.10-rc2
> continues to look pretty good but the content there varies based on what
> was given to me in the PR. So please, the more details in the request
> the better!
>
> I'm still planning on doing -rc3 on the 26th of August with -rc4 on
> September 9th and -rc5 on September 23rd with the release scheduled on
> October 7th. Thanks all!
I'm seeing the following build failure with gcc 9, possibly due to
tightened cflags in Fedora, although from a quick look I don't see
why, since the split out of environment functions into the separate
header. Any thoughts on what might be missing?
Peter
BUILDSTDERR: gcc -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
-fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-Wp,-MD,scripts/dtc/.checks.o.d -Iscripts/dtc -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -std=gnu11
-I../scriptsIn file included from ../tools/env/../../env/flags.c:7,
BUILDSTDERR: from ../tools/env/env_flags.c:1:
BUILDSTDERR: ../include/env.h:158:1: error: unknown type name 'ulong';
did you mean 'long'?
BUILDSTDERR: 158 | ulong env_get_ulong(const char *name, int base,
ulong default_val);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: | long
BUILDSTDERR: ../include/env.h:158:49: error: unknown type name
'ulong'; did you mean 'long'?
BUILDSTDERR: 158 | ulong env_get_ulong(const char *name, int base,
ulong default_val);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: | long
BUILDSTDERR: ../include/env.h:167:40: error: unknown type name
'ulong'; did you mean 'long'?
BUILDSTDERR: 167 | int env_set_ulong(const char *varname, ulong value);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: | long
BUILDSTDERR: ../include/env.h:179:1: error: unknown type name 'ulong';
did you mean 'long'?
BUILDSTDERR: 179 | ulong env_get_hex(const char *varname, ulong default_val);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: | long
BUILDSTDERR: ../include/env.h:179:40: error: unknown type name
'ulong'; did you mean 'long'?
BUILDSTDERR: 179 | ulong env_get_hex(const char *varname, ulong default_val);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: | long
BUILDSTDERR: ../include/env.h:188:38: error: unknown type name
'ulong'; did you mean 'long'?
BUILDSTDERR: 188 | int env_set_hex(const char *varname, ulong value);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: | long
BUILDSTDERR: ../include/env.h: In function 'env_set_addr':
BUILDSTDERR: ../include/env.h:199:31: error: 'ulong' undeclared (first
use in this function)
BUILDSTDERR: 199 | return env_set_hex(varname, (ulong)addr);
BUILDSTDERR: | ^~~~~
BUILDSTDERR: ../include/env.h:199:31: note: each undeclared identifier
is reported only once for each function it appears in
BUILDSTDERR: ../include/env.h:199:37: error: expected ')' before 'addr'
BUILDSTDERR: 199 | return env_set_hex(varname, (ulong)addr);
BUILDSTDERR: | ^~~~
BUILDSTDERR: | )
BUILDSTDERR: ../include/env.h: At top level:
BUILDSTDERR: ../include/env.h:223:44: error: unknown type name 'uint8_t'
BUILDSTDERR: 223 | int eth_env_get_enetaddr(const char *name,
uint8_t *enetaddr);
BUILDSTDERR: | ^~~~~~~
BUILDSTDERR: ../include/env.h:232:50: error: unknown type name 'uint8_t'
BUILDSTDERR: 232 | int eth_env_set_enetaddr(const char *name, const
uint8_t *enetaddr);
BUILDSTDERR: | ^~~~~~~
BUILDSTDERR: make[2]: *** [scripts/Makefile.host:114:
tools/env/env_flags.o] Error 1
BUILDSTDERR: make[1]: ***
[/builddir/build/BUILD/u-boot-2019.10-rc2/Makefile:1778: envtools]
Error 2
BUILDSTDERR: make[1]: *** Waiting for unfinished jobs....
BUILDSTDERR: make: *** [Makefile:148: sub-make] Error 2
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] [ANN] U-Boot v2019.10-rc2 released
2019-08-21 8:23 ` Peter Robinson
@ 2019-08-24 1:50 ` David Abdurachmanov
2019-08-26 7:01 ` Heiko Schocher
0 siblings, 1 reply; 4+ messages in thread
From: David Abdurachmanov @ 2019-08-24 1:50 UTC (permalink / raw)
To: u-boot
On Wed, Aug 21, 2019 at 1:24 AM Peter Robinson <pbrobinson@gmail.com> wrote:
>
> Hi Simon,
>
> > It's the day after the scheduled release day, and here is v2019.10-rc2.
> > It took me a while to confirm that the riscv PR was causing the issue I
> > saw, and I got extra paranoid about testing all of the other PRs to be
> > sure it really was that and not some other race condition. At this
> > point, it's time to aim to stabilize everything. That said, I think
> > there's at least one or two trees that haven't sent their big PR yet and
> > I'd like to see that come in as soon as possible.
> >
> > In terms of a changelog,
> > git log --merges v2019.10-rc1..v2019.10-rc2
> > continues to look pretty good but the content there varies based on what
> > was given to me in the PR. So please, the more details in the request
> > the better!
> >
> > I'm still planning on doing -rc3 on the 26th of August with -rc4 on
> > September 9th and -rc5 on September 23rd with the release scheduled on
> > October 7th. Thanks all!
>
> I'm seeing the following build failure with gcc 9, possibly due to
> tightened cflags in Fedora, although from a quick look I don't see
> why, since the split out of environment functions into the separate
> header. Any thoughts on what might be missing?
I hit the same issue on RISC-V.
Looks like env.h incl. linux/types.h (the internal one in U-Boot
provides ulong).
Then IIUC all U-Boot incl. are added via -idirafter flag thus we probably
incl. /usr/include/linux/types.h from the system which doesn't have these
typedefs. I haven't verified it via a local build thus it's just a guess.
>
> Peter
>
> BUILDSTDERR: gcc -O2 -g -pipe -Wall -Werror=format-security
> -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
> -fstack-protector-strong -grecord-gcc-switches
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> -Wp,-MD,scripts/dtc/.checks.o.d -Iscripts/dtc -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -std=gnu11
> -I../scriptsIn file included from ../tools/env/../../env/flags.c:7,
> BUILDSTDERR: from ../tools/env/env_flags.c:1:
> BUILDSTDERR: ../include/env.h:158:1: error: unknown type name 'ulong';
> did you mean 'long'?
> BUILDSTDERR: 158 | ulong env_get_ulong(const char *name, int base,
> ulong default_val);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: | long
> BUILDSTDERR: ../include/env.h:158:49: error: unknown type name
> 'ulong'; did you mean 'long'?
> BUILDSTDERR: 158 | ulong env_get_ulong(const char *name, int base,
> ulong default_val);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: | long
> BUILDSTDERR: ../include/env.h:167:40: error: unknown type name
> 'ulong'; did you mean 'long'?
> BUILDSTDERR: 167 | int env_set_ulong(const char *varname, ulong value);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: | long
> BUILDSTDERR: ../include/env.h:179:1: error: unknown type name 'ulong';
> did you mean 'long'?
> BUILDSTDERR: 179 | ulong env_get_hex(const char *varname, ulong default_val);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: | long
> BUILDSTDERR: ../include/env.h:179:40: error: unknown type name
> 'ulong'; did you mean 'long'?
> BUILDSTDERR: 179 | ulong env_get_hex(const char *varname, ulong default_val);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: | long
> BUILDSTDERR: ../include/env.h:188:38: error: unknown type name
> 'ulong'; did you mean 'long'?
> BUILDSTDERR: 188 | int env_set_hex(const char *varname, ulong value);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: | long
> BUILDSTDERR: ../include/env.h: In function 'env_set_addr':
> BUILDSTDERR: ../include/env.h:199:31: error: 'ulong' undeclared (first
> use in this function)
> BUILDSTDERR: 199 | return env_set_hex(varname, (ulong)addr);
> BUILDSTDERR: | ^~~~~
> BUILDSTDERR: ../include/env.h:199:31: note: each undeclared identifier
> is reported only once for each function it appears in
> BUILDSTDERR: ../include/env.h:199:37: error: expected ')' before 'addr'
> BUILDSTDERR: 199 | return env_set_hex(varname, (ulong)addr);
> BUILDSTDERR: | ^~~~
> BUILDSTDERR: | )
> BUILDSTDERR: ../include/env.h: At top level:
> BUILDSTDERR: ../include/env.h:223:44: error: unknown type name 'uint8_t'
> BUILDSTDERR: 223 | int eth_env_get_enetaddr(const char *name,
> uint8_t *enetaddr);
> BUILDSTDERR: | ^~~~~~~
> BUILDSTDERR: ../include/env.h:232:50: error: unknown type name 'uint8_t'
> BUILDSTDERR: 232 | int eth_env_set_enetaddr(const char *name, const
> uint8_t *enetaddr);
> BUILDSTDERR: | ^~~~~~~
> BUILDSTDERR: make[2]: *** [scripts/Makefile.host:114:
> tools/env/env_flags.o] Error 1
> BUILDSTDERR: make[1]: ***
> [/builddir/build/BUILD/u-boot-2019.10-rc2/Makefile:1778: envtools]
> Error 2
> BUILDSTDERR: make[1]: *** Waiting for unfinished jobs....
> BUILDSTDERR: make: *** [Makefile:148: sub-make] Error 2
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] [ANN] U-Boot v2019.10-rc2 released
2019-08-24 1:50 ` David Abdurachmanov
@ 2019-08-26 7:01 ` Heiko Schocher
0 siblings, 0 replies; 4+ messages in thread
From: Heiko Schocher @ 2019-08-26 7:01 UTC (permalink / raw)
To: u-boot
Hello David,
Am 24.08.2019 um 03:50 schrieb David Abdurachmanov:
> On Wed, Aug 21, 2019 at 1:24 AM Peter Robinson <pbrobinson@gmail.com> wrote:
>>
>> Hi Simon,
>>
>>> It's the day after the scheduled release day, and here is v2019.10-rc2.
>>> It took me a while to confirm that the riscv PR was causing the issue I
>>> saw, and I got extra paranoid about testing all of the other PRs to be
>>> sure it really was that and not some other race condition. At this
>>> point, it's time to aim to stabilize everything. That said, I think
>>> there's at least one or two trees that haven't sent their big PR yet and
>>> I'd like to see that come in as soon as possible.
>>>
>>> In terms of a changelog,
>>> git log --merges v2019.10-rc1..v2019.10-rc2
>>> continues to look pretty good but the content there varies based on what
>>> was given to me in the PR. So please, the more details in the request
>>> the better!
>>>
>>> I'm still planning on doing -rc3 on the 26th of August with -rc4 on
>>> September 9th and -rc5 on September 23rd with the release scheduled on
>>> October 7th. Thanks all!
>>
>> I'm seeing the following build failure with gcc 9, possibly due to
>> tightened cflags in Fedora, although from a quick look I don't see
>> why, since the split out of environment functions into the separate
>> header. Any thoughts on what might be missing?
>
> I hit the same issue on RISC-V.
>
> Looks like env.h incl. linux/types.h (the internal one in U-Boot
> provides ulong).
> Then IIUC all U-Boot incl. are added via -idirafter flag thus we probably
> incl. /usr/include/linux/types.h from the system which doesn't have these
> typedefs. I haven't verified it via a local build thus it's just a guess.
>
Please try the patches from Pierre-Jean:
http://patchwork.ozlabs.org/patch/1152434/
http://patchwork.ozlabs.org/patch/1152435/
http://patchwork.ozlabs.org/patch/1152436/
They helped me out of the issue.
bye,
Heiko
>>
>> Peter
>>
>> BUILDSTDERR: gcc -O2 -g -pipe -Wall -Werror=format-security
>> -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
>> -fstack-protector-strong -grecord-gcc-switches
>> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
>> -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
>> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
>> -Wp,-MD,scripts/dtc/.checks.o.d -Iscripts/dtc -Wall
>> -Wstrict-prototypes -O2 -fomit-frame-pointer -std=gnu11
>> -I../scriptsIn file included from ../tools/env/../../env/flags.c:7,
>> BUILDSTDERR: from ../tools/env/env_flags.c:1:
>> BUILDSTDERR: ../include/env.h:158:1: error: unknown type name 'ulong';
>> did you mean 'long'?
>> BUILDSTDERR: 158 | ulong env_get_ulong(const char *name, int base,
>> ulong default_val);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: | long
>> BUILDSTDERR: ../include/env.h:158:49: error: unknown type name
>> 'ulong'; did you mean 'long'?
>> BUILDSTDERR: 158 | ulong env_get_ulong(const char *name, int base,
>> ulong default_val);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: | long
>> BUILDSTDERR: ../include/env.h:167:40: error: unknown type name
>> 'ulong'; did you mean 'long'?
>> BUILDSTDERR: 167 | int env_set_ulong(const char *varname, ulong value);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: | long
>> BUILDSTDERR: ../include/env.h:179:1: error: unknown type name 'ulong';
>> did you mean 'long'?
>> BUILDSTDERR: 179 | ulong env_get_hex(const char *varname, ulong default_val);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: | long
>> BUILDSTDERR: ../include/env.h:179:40: error: unknown type name
>> 'ulong'; did you mean 'long'?
>> BUILDSTDERR: 179 | ulong env_get_hex(const char *varname, ulong default_val);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: | long
>> BUILDSTDERR: ../include/env.h:188:38: error: unknown type name
>> 'ulong'; did you mean 'long'?
>> BUILDSTDERR: 188 | int env_set_hex(const char *varname, ulong value);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: | long
>> BUILDSTDERR: ../include/env.h: In function 'env_set_addr':
>> BUILDSTDERR: ../include/env.h:199:31: error: 'ulong' undeclared (first
>> use in this function)
>> BUILDSTDERR: 199 | return env_set_hex(varname, (ulong)addr);
>> BUILDSTDERR: | ^~~~~
>> BUILDSTDERR: ../include/env.h:199:31: note: each undeclared identifier
>> is reported only once for each function it appears in
>> BUILDSTDERR: ../include/env.h:199:37: error: expected ')' before 'addr'
>> BUILDSTDERR: 199 | return env_set_hex(varname, (ulong)addr);
>> BUILDSTDERR: | ^~~~
>> BUILDSTDERR: | )
>> BUILDSTDERR: ../include/env.h: At top level:
>> BUILDSTDERR: ../include/env.h:223:44: error: unknown type name 'uint8_t'
>> BUILDSTDERR: 223 | int eth_env_get_enetaddr(const char *name,
>> uint8_t *enetaddr);
>> BUILDSTDERR: | ^~~~~~~
>> BUILDSTDERR: ../include/env.h:232:50: error: unknown type name 'uint8_t'
>> BUILDSTDERR: 232 | int eth_env_set_enetaddr(const char *name, const
>> uint8_t *enetaddr);
>> BUILDSTDERR: | ^~~~~~~
>> BUILDSTDERR: make[2]: *** [scripts/Makefile.host:114:
>> tools/env/env_flags.o] Error 1
>> BUILDSTDERR: make[1]: ***
>> [/builddir/build/BUILD/u-boot-2019.10-rc2/Makefile:1778: envtools]
>> Error 2
>> BUILDSTDERR: make[1]: *** Waiting for unfinished jobs....
>> BUILDSTDERR: make: *** [Makefile:148: sub-make] Error 2
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> https://lists.denx.de/listinfo/u-boot
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52 Fax: +49-8142-66989-80 Email: hs at denx.de
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-08-26 7:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-13 22:26 [U-Boot] [ANN] U-Boot v2019.10-rc2 released Tom Rini
2019-08-21 8:23 ` Peter Robinson
2019-08-24 1:50 ` David Abdurachmanov
2019-08-26 7:01 ` Heiko Schocher
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.